GWAS Catalog Model Context Protocol (MCP) server providing access to curated results from the GWAS Catalog, a database of published human genome-wide association (GWAS) studies
Three well-structured read-only tools with comprehensive input schemas and clear descriptions. All tools have detailed parameter definitions with type constraints (patterns, enums, min/max). Descriptions are action-oriented and explain query capabilities. Output schemas are documented via ToolResponse wrapper with pagination and suggestions. Naming follows verb_noun convention (get_*). Main gaps: no error handling guidance in descriptions, no per-parameter descriptions visible in schema (only in code comments), and no tool annotations (readOnlyHint, idempotentHint) declared in MCP registration.
Returns: SNP-trait association records. Query by: association ID, trait, gene, variant, study accession, PubMed ID
Returns: GWAS study metadata. Query by: study accession, trait, gene, ancestry, cohort, PubMed ID
Returns: EFO trait metadata. Query by: EFO ID, trait name, mapped gene, PubMed ID, URI
Tool descriptions lack error recovery guidance. No mention of what to do if a query returns no results, how to broaden searches, or when to try alternative parameters.
Tool annotations (readOnlyHint, idempotentHint) not declared in MCP tool registration. While tools are read-only, explicit annotations enable agents to reason about safety and retry semantics.
Parameter descriptions exist in code but may not be fully visible in JSON Schema. Verify all 30+ parameters have inline descriptions in the schema definition, not just in comments.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | A | 81 | 2026-07-28+ | v2 |
Output schema documentation is implicit (via ToolResponse model). Add explicit 'returns' section to tool descriptions stating: 'Returns a ToolResponse containing: data (list of results), pagination (page/total_results/truncated), suggestions (actionable next steps), message (if no results).'
No guidance on pagination limits or result truncation in tool descriptions. Agents should know upfront that results are capped at 50 per page and how to request additional pages.