Skip to main content
Glama

search_microbial_catalog

Search the NMDC microbial catalog by keyword to find global microbial names, Chinese fungal specimens, and fungal names, with paginated results.

Instructions

Search the microbial catalog on NMDC. Includes global microbial names, Chinese fungal specimens, and fungal names.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-indexed), default: 1
sizeNoNumber of results per page, default: 20
keywordNoSearch keyword (e.g., species name, specimen ID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 burden; it does add useful corpus scope (which three collections are searched), which no structured field provides. It omits behavior an agent would want: result ordering, what happens when keyword is omitted (all parameters are optional), and whether an empty search returns the whole catalog.

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 scope front-loaded and no filler. Slight redundancy between "microbial catalog" and "microbial names" keeps it from being maximally tight.

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?

A simple three-parameter, all-optional search tool with no output schema, so it needn't document return values. However, with no annotations and no routing guidance among numerous search siblings, an agent is left to guess both the result shape and when this tool is the right choice.

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 defaults and bounds. The description adds no additional meaning about keyword matching semantics (exact vs. fuzzy, which fields are matched) beyond the schema.

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 the microbial catalog on NMDC") and enumerates the corpora covered: global microbial names, Chinese fungal specimens, and fungal names. An agent can tell what data it reaches, though it is not distinguished from siblings like search_microbial_dictionary or search_fungi.

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?

No when-to-use guidance and no mention of when to prefer this over the many sibling search tools (search_microbial_dictionary, search_fungi, search_pathogen). Usage is only inferable from the word "search".

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