Skip to main content
Glama

search_nmdc_data

Search all NMDC microbiology databases by keyword to retrieve matching BioProjects, BioSamples, sequences, genomes, and related records, with optional category filters and pagination.

Instructions

Search for data across all NMDC (National Microbiology Data Center) databases. Returns matching records including BioProjects, BioSamples, sequences, genomes, etc. Use this tool when you need to find microbiology data by keyword.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keyword": "<keyword>"
    },
    "name": "search_nmdc_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-indexed), default: 1
sizeNoNumber of results per page, default: 20
keywordYesSearch keyword (e.g., organism name, gene name, sequence ID)
categoryNoData category to filter search results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does communicate that this is a read-style lookup returning matching records of several types. It says nothing about pagination behavior, result caps, ordering, or whether a total count is returned, which matters for a cross-database search with page/size controls.

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?

Three short sentences, front-loaded with scope and then return types, with no filler. The trailing "etc." in the record list is the only soft spot, mildly diluting a otherwise crisp enumeration.

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 four-parameter search tool with fully documented parameters and no output schema, the description covers purpose and rough return content. It is incomplete regarding how results are paged or ordered and how this broad search relates to the specialized sibling tools, which an agent needs to invoke it well.

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%, including enum values for category and defaults/ranges for page and size, so the baseline is 3. The description adds no meaning beyond the schema, mentioning only keyword-based searching, which is already documented.

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 for data across all NMDC databases") and enumerates the record types returned (BioProjects, BioSamples, sequences, genomes). It does not distinguish itself from the many sibling search tools such as search_genome, search_virus, or search_sra, so the agent cannot tell from this text alone when the broad search is preferable.

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

Usage Guidelines3/5

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

"Use this tool when you need to find microbiology data by keyword" gives only a generic trigger with no exclusions and no named alternatives. Given a catalog containing a dozen specialized search_* siblings, the absence of any routing guidance (e.g., prefer the category-specific tool when known) leaves the choice to inference.

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