Skip to main content
Glama

search_genome

Search NMDC genome records by organism name to locate relevant microbial genomes, with page and size controls for browsing results.

Instructions

Search for genome records in the NMDC database. Can filter by organism name.

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_genome"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-indexed), default: 1
sizeNoNumber of results per page, default: 20
organismNoOrganism name to filter by (e.g., 'Escherichia coli')

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?

With no annotations supplied, the description carries the full disclosure burden. 'Search' implies a read-only operation, but nothing is said about whether results are paginated (the schema has page/size), what a genome record contains, whether an empty result is possible, or any rate limits. For an unannotated tool this leaves too much undisclosed.

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 with the resource and the filter option front-loaded; there is no filler. It is perhaps too terse rather than padded, but every sentence does contribute.

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

Completeness2/5

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

For a three-parameter search tool with no annotations and no output schema, the definition should say what is returned and how pagination relates to total results, since the output schema cannot supply that. It covers the filter but leaves the result shape and paging semantics entirely unexplained.

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 organism are already documented with defaults and ranges in the schema itself. The description only restates the organism filter and adds no syntax or matching semantics (exact vs. substring, case sensitivity), so the baseline of 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?

States a specific verb and resource: search genome records in the NMDC database. It does not differentiate itself from the many sibling search_* tools (search_sra, search_metagenome, search_virus), so an agent must still infer that 'genome records' means assembled genomes rather than reads or metagenomes.

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?

The only guidance is the clause 'Can filter by organism name', which describes a parameter rather than a use case. There is no statement of when to choose this over search_sra or search_metagenome, and no exclusions or prerequisites are given.

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