MCP server for querying glycosylation site and glycan information from the GlyCosmos API
Single tool with adequate naming (verb_noun pattern) but significant gaps in description depth and parameter documentation. Tool description is 108 chars (within 10-1024 range) but lacks WHEN/WHY context. Input schema present with type and description, but output schema is complex nested structure without field-level descriptions. No error handling guidance, no pagination despite potential for large result sets, no rate limiting or timeout documentation. Missing security considerations for external API calls.
Get the glycosylation site and glycan information for a given UniProt ID.
Output schema lacks field-level descriptions. GlycanInfo model has 5 fields (position, description, pubmed_ids, glytoucan_ids, source) but only top-level description exists. LLM cannot understand what each field represents or how to use nested structures.
No error handling or recovery guidance. Tool calls external API (api.glycosmos.org) with no documented timeout, retry logic, or error messages. If API fails, LLM receives raw exception with no actionable next step.
No pagination or result limiting documented. Tool returns potentially unbounded list of glycosylation sites. Large responses could exhaust context window. No limit parameter, no offset/page support, no total count in response.
Tool description lacks WHEN/WHY context. Current description only states WHAT (get glycosylation info) but not WHEN to call it or what prerequisites exist. LLM cannot determine if this is the right tool for a given task.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
Parameter description includes example value 'Q9NR99' in docstring. LLMs tend to reuse example values literally rather than adapting to context, risking incorrect calls.