Skip to main content
Glama

Taxonomy Search

taxonomy_search
Read-onlyIdempotent

"NCBI taxonomy ID for [organism]" / "taxid for [species]" / "look up [Latin name] in NCBI taxonomy", search NCBI Taxonomy via UniProt's mirror. Returns taxonomic IDs you can use as organism_id filters in search (9606 = human, 10090 = mouse, 7227 = D. melanogaster, etc).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
sizeNo
queryYes

Output Schema

NameRequiredDescriptionDefault
facetsNoSearch facets
resultsNoArray of taxonomy entries

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely new context the annotations lack: the data comes from a mirror of NCBI Taxonomy rather than NCBI directly, and the return values are IDs intended for downstream filtering. It says nothing about result limits or ordering, which keeps it below 5.

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?

Compact and front-loaded with the user phrasings that trigger it, followed by source and downstream usage; no filler sentences. The quoting of trigger phrases is slightly noisy but functional, and the ID parenthetical is informative rather than repetitive.

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?

For a two-parameter, read-only lookup with an output schema (so return values need no explanation), the description covers source, intent, and downstream use well. The only real gap is the `size` parameter and any guidance on result caps or empty queries.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden, and it only partially does: `query` is illustrated through example phrasings implying organism or Latin name, but the `size` parameter is never mentioned in the description or the schema, leaving its meaning and default unknown. A 3 baseline is not available here because coverage is at zero and one parameter is entirely undocumented.

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

Purpose5/5

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

States a specific verb and resource ('search NCBI Taxonomy'), names the data pathway (UniProt's mirror), and states what the output is used for (taxonomic IDs as organism_id filters in `search`), with concrete ID examples. An agent can tell this apart from uniprot_search or proteomes_search without opening a schema.

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

Usage Guidelines4/5

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

The quoted trigger phrasings ('NCBI taxonomy ID for [organism]', 'look up [Latin name]') give clear arrival conditions, and the description explicitly routes the output into `search` as an organism_id filter. It does not state when to prefer a sibling taxonomy source or what to do if no match is found, so it stops short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.