Skip to main content
Glama

search_microbial_dictionary

Search NMDC's microbial dictionary for biological and microbiological terms, including English-Chinese, paleontological, and molecular biology vocabulary, with paginated results.

Instructions

Search the microbial dictionary on NMDC for biological and microbiological terms. Includes English-Chinese biological terms, paleontological vocabulary, and molecular biology terms.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-indexed), default: 1
sizeNoNumber of results per page, default: 20
keywordYesSearch keyword (biological term to look up)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 disclose the scope of the underlying vocabulary, which is useful, but it never states that the operation is a read-only lookup, says nothing about permissions, and does not describe the shape of returned entries beyond the schema's pagination fields.

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 no filler; the core purpose and content scope are front-loaded. The second sentence could be tightened but nothing is redundant.

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

Completeness4/5

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

A simple paginated read tool with a fully described three-parameter schema and no output schema. The one remaining gap is that it does not hint at what a result entry contains (definitions, translations, term identifiers), which would help an agent interpret the response.

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 keyword, page and size are already fully documented in the schema. The description adds no matching semantics such as whether matching is exact, prefix, or substring, or how the English/Chinese terms relate to a keyword.

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?

Names a specific verb (Search) and resource (the microbial dictionary on NMDC), and the second sentence scopes the content to English-Chinese biological, paleontological and molecular biology vocabulary. It is distinguishable from data-retrieval siblings like search_microbial_catalog, though it never explicitly contrasts with them.

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?

Usage is only implied: an agent can infer this is for looking up term definitions/translations rather than retrieving datasets. There is no explicit when-to-use, when-not-to-use, or named alternative among the many search_* siblings.

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