Sofia Ferro's portfolio MCP server demonstrates solid fundamentals with well-named tools following verb_noun conventions (get_resume, list_projects, get_project, get_manifesto, contact). All tools have substantive descriptions (130 - 280 chars, well within the 10 - 1024 baseline). Input schemas are explicit with Zod validation and descriptions present. However, output schemas are not formally documented, responses are returned as text JSON without explicit schema declarations in tool registration. Error handling exists for the contact tool (rate limiting) but lacks recovery guidance for edge cases (e.g., email service failures). Tool composition is clean: single-responsibility tools with good chaining (list_projects → get_project via slug). The contact tool properly declares itself as WRITE-risk, though permission checks and audit trail patterns are minimal. Descriptions appropriately reference canonical URLs and dependency hints ('Use list_projects first to discover valid slugs'), following mxe:natural-identifiers guidance by accepting human-friendly locales.

• Add explicit outputSchema to each tool's registerTool() call. Define the structure of JSON Resume fields (basics, skills, work, projects), project list items (slug, title, summary, category, date, tech, links), and full project response (all metadata + markdown body). Use Zod schemas and document them.
• Wrap error responses in structured format with an actionable 'next_steps' or 'suggested_action' field. For contact rate-limit: return {"isError": true, "message": "Rate limited. Email [email protected] directly or try again in 10 minutes."}
• Add optional limit and offset/cursor parameters to list_projects for pagination. Default limit=20, max=100. Document in description: 'Returns max 20 projects per page; use offset or next_cursor for additional results.'
• Remove the ignored locale parameter from get_resume, or implement i18n for the resume. Accepting a parameter that has no effect trains LLMs to ignore parameter documentation.
• Add per-request error context. When contact fails (email service down, rate limit exceeded, validation error), return the invalid field name and constraint violated: 'Invalid message length: 2500 > 2000 max. Truncate and retry.'
• Add scope/permission declarations in tool descriptions. E.g., contact tool: 'Requires permission: write:email. Rate limited to 5 calls per 10 minutes per IP.'
• Consider adding a get_contact_status or contact_check tool that LLMs can call to see if contact is available and rate limit remaining, enabling smarter retry logic.
• Return consistent field names across responses. If list_projects returns 'tech' (array), ensure get_project also uses 'tech', do not rename to 'technologies' or 'stack'.