Skip to main content
Glama

search_tuberculosis

Search NMDC for tuberculosis data, including Mycobacterium tuberculosis genomes and clinical records, to find and review relevant microbiology records.

Instructions

Search tuberculosis data on NMDC. Includes Mycobacterium tuberculosis genome and clinical data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_tuberculosis"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-indexed), default: 1
sizeNoNumber of results per page, default: 20
keywordNoSearch keyword

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it delivers very little: it never states that this is a read-only operation, how results are ordered or paginated, whether authentication is required, or what the response shape looks like. The one useful hint is the content scope ('genome and clinical data'), which is thin for a tool with zero annotation coverage.

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

Conciseness4/5

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

Two short sentences, front-loaded with the purpose and with no filler. The second sentence is slightly vague but earns its place by scoping the data included.

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

Completeness3/5

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

For a simple three-parameter search with full schema coverage, the description is adequate at the minimum-viable level. However, with no annotations and no output schema, it should say more about what a result record contains and how pagination behaves.

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 description coverage is 100%, so page, size, and keyword are already fully documented with types, defaults, and bounds. The description adds no extra meaning about keyword matching behavior (case sensitivity, field targeting, phrase handling), so the baseline 3 applies.

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

Purpose4/5

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

The description names a specific verb and resource ('Search tuberculosis data on NMDC') and narrows the content domain to M. tuberculosis genome and clinical data, which distinguishes it from generic siblings like search_nmdc_data or search_pathogen. It stops short of explicitly naming which sibling to use for broader searches, so it misses the top mark.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of the obvious alternative (search_pathogen or search_nmdc_data) for non-tuberculosis queries. The only signal is the implied subject matter in the tool name and first sentence.

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