Skip to main content
Glama

disease_lookup

Look up a canine inherited disease by name or OMIA id -> its governed OMIA clinical record (inheritance, causal gene(s), curated description, clinical signs, human OMIM analog + Mondo id, evidence base). Sourced to OMIA (CC-BY); returns a canonical sniff.world URL. Dog-only. For candidate disambiguation use search_diseases; for a disease's molecular links use disease_links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Describes content of returned record (inheritance, causal genes, etc.), sourcing, and URL. No annotations, but description implies read-only. Could be more explicit about lack of side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no wasted words. Purpose is front-loaded. Includes necessary context and sibling references concisely.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given presence of output schema, description adequately covers the lookup operation, return content, constraints, and relationships to siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has no parameter descriptions (0% coverage). Description says query can be disease name or OMIA id, adding meaning beyond the schema. However, lacks format or examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states action (look up), resource (canine inherited disease), and result (OMIA clinical record with details). Distinguishes from siblings by naming search_diseases for disambiguation and disease_links for molecular links.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use this tool vs alternatives: for candidate disambiguation use search_diseases, for molecular links use disease_links. Also specifies constraint: dog-only.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

Tools are mostly distinct with clear purposes, but some overlap exists between disease-related tools (disease_lookup vs disease_links) and between ask and ask_the_graph. Descriptions help differentiate, but an agent might still misselect.

Naming Consistency2/5

Naming patterns are inconsistent: some tools use verb_noun (ask, search_diseases), others use noun_noun (breed_similarity, disease_bridge), and some use descriptive phrases. No consistent convention observed.

Tool Count5/5

18 tools is well-scoped for a canine genetics knowledge base. Each tool serves a distinct function covering breed, disease, variant, and query capabilities without being overwhelming.

Completeness5/5

The tool set covers all major aspects of the domain: breed profiles, disease lookup with links, variant querying, semantic search, and metadata. No obvious gaps for the stated educational purpose.