Skip to main content
Glama
Sign In

apibase

by io.github.whiteknightonhorse
OverviewDiscussionsAdmin

NCBI Taxonomy Summary

ncbi-eutils.taxonomy.summary
Read-onlyIdempotent

Get the scientific name, common name, taxonomic rank, and division for one NCBI TaxID. Use ncbi-eutils.taxonomy_search first to find a tax_id. For the full kingdom-to-species classification tree, use ncbi-eutils.taxonomy_lineage instead. Data: eutils.ncbi.nlm.nih.gov, no auth required.

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": {
      "tax_id": "<tax_id>"
    },
    "name": "ncbi-eutils.taxonomy.summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
tax_idYesNCBI Taxonomy ID (e.g. "9689" for Panthera leo), from ncbi-eutils.taxonomy_search results

Output Schema

NameRequiredDescriptionDefault
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety and idempotency. The description adds value by noting the data source (eutils.ncbi.nlm.nih.gov) and that no auth is required, which is useful context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three well-structured sentences: the first states what it returns, the second gives the prerequisite workflow, and the third offers the alternative. No wasted words, and the most important information is front-loaded.

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

Completeness5/5

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

For a simple one-parameter lookup with a full output schema and comprehensive annotations, the description covers purpose, usage, alternative, and data source. Nothing an agent needs to correctly invoke this tool is missing.

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%, and the schema already explains tax_id thoroughly (pattern, example, source from taxonomy_search). The description adds no new parameter-level information, but it reinforces the workflow. With high schema coverage, baseline 3 is appropriate.

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?

The description clearly states the tool retrieves scientific name, common name, rank, and division for a single NCBI TaxID, and distinguishes it from lineage (full tree) and search (finding IDs). This is a specific verb+resource with clear sibling differentiation.

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

Usage Guidelines5/5

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

Explicitly instructs to use taxonomy_search first to obtain a tax_id, and directs users to taxonomy_lineage for full classification trees. This provides clear when-to-use and when-not-to-use guidance with named alternatives.

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

All apibase toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources