MCP server providing tools for multiple applications: Trip Planner (geocoding), Resume Maker (ATS analysis), Text Editor (style guides), and Invitation Maker (design resources)
Four tools with basic schemas and descriptions, but significant quality gaps. All tools have input schemas with enums and descriptions, meeting minimum requirements. However, descriptions are generic (avg 95 chars, below 194-char baseline), lack context on WHEN to use each tool, and do not explain output structure. No output schemas documented. Parameters lack format constraints and dependency documentation. Tool names use underscores but lack clear verb-noun patterns (e.g., 'geocoding' is a noun, not a verb; 'ats_analyzer' is vague about what analysis occurs). No error handling guidance visible. No security considerations documented despite tools handling sensitive data (resumes, job descriptions, religious/cultural information). Composition is reasonable (each tool has one concern), but parameter relationships are undocumented.
Analyze resumes for ATS optimization and extract keywords from job descriptions
Access design templates, cultural patterns, and language resources for invitations
Calculate distances between locations and optimize routes
Access style guides, grammar rules, and tone dictionaries for text editing
Tool names lack action verbs. 'geocoding' is a noun; should be 'calculate_distance' or 'optimize_route'. 'ats_analyzer' is vague, does it score, extract, or parse? LLMs cannot infer intent from noun-based names.
No output schemas documented. Tools return data but LLMs cannot plan downstream calls or extract fields. E.g., does 'geocoding' return lat/lon, distance in km/miles, or a route object? Undocumented outputs force LLMs to guess.
Descriptions are generic and lack context. 'Analyze resumes for ATS optimization' does not explain WHEN to call this vs. other tools, what 'optimization' means, or what the output contains. Descriptions should be 50-200 chars and answer: what, when, why.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 38 | 2026-07-28+ | v2 |
design_resources tool exposes sensitive cultural/religious parameters (religion enum: hindu, muslim, christian, sikh) without documented permission checks or audit logging. No indication of how this data is handled or who can access it.
Parameters lack format constraints and dependency documentation. E.g., 'from' and 'to' in geocoding have no format (address string? lat/lon? place name?). 'action' enum is required but other params are optional with no guidance on which combinations are valid.