MCP server providing access to NUM's place search and agent API services
Single tool with basic schema and minimal description. Tool name 'num_search_places' follows verb_noun convention but description is only 40 chars (below 50-200 char baseline for LLM-optimized descriptions). Input schema present with types and descriptions for all 3 parameters, but output schema is completely undocumented, LLMs cannot plan downstream calls or extract results. No error handling guidance, no pagination despite search returning multiple results, no rate limiting or result limits documented. No tool annotations (readOnlyHint present via Risk field but not in schema). Server is HTTP-based (good) but tool definition quality is mediocre.
Search for places by city and category
Output schema completely undocumented. LLMs cannot know what fields to expect from search results, preventing downstream tool chaining and forcing unstructured parsing.
Tool description is only 40 characters ('Search for places by city and category'). Baseline for LLM-optimized descriptions is 50-200 chars. Lacks context on when to use this tool vs alternatives, what results look like, and any prerequisites.
No pagination support documented. Search tools returning multiple results must accept limit/offset and return total count or next_cursor. Current 'limit' parameter has no documented max or default, inviting unbounded requests.
No error handling guidance. If city not found or category invalid, LLM receives no recovery path. Should return 'City not found. Available cities: Bangkok, Phuket, Chiang Mai' or similar.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2026-07-28+ | v2 |
Tool annotations missing from schema. Risk field in metadata indicates READ_ONLY but schema lacks readOnlyHint annotation. Agents cannot infer safety from schema alone.