Skip to main content
Glama

biothings_get_taxon

Fetch detailed taxonomic information for any NCBI taxon ID or scientific name, including lineage, rank, and gene data availability.

Instructions

Fetch a specific taxon by NCBI ID or scientific name.

    Retrieves detailed information about a specific taxon using its identifier.
    
    **Supported Identifiers:**
    - NCBI ID: 9606 (Homo sapiens)
    - Scientific name: "Homo sapiens"
    
    Returns comprehensive taxon information including basic information (ID, scientific name, common name),
    taxonomic classification (rank, parent taxon), lineage information, alternative names and authorities,
    and gene data availability.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNo
fieldsNoall
taxon_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_idYesTaxon identifier
rankNoTaxonomic rank
taxidNoTaxon ID
lineageNoTaxonomic lineage IDs
_versionNoVersion number
has_geneNoWhether the taxon has gene data
authorityNoTaxonomic authority
common_nameNoCommon name
other_namesNoOther names
parent_taxidNoParent taxon ID
uniprot_nameNoUniProt name
scientific_nameNoScientific name
genbank_common_nameNoGenBank common name
Behavior4/5

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

No annotations are provided, so the description fully carries behavioral disclosure. It explains that the tool returns comprehensive taxon information, lists included categories (basic info, classification, lineage, etc.), and mentions supported identifier types. It lacks mention of authentication or rate limits, but for a read-only tool this is adequate.

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?

The description is well-structured with clear sections and bullet points. It efficiently conveys key information without extraneous text. Every sentence adds value.

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?

Given the presence of an output schema, the description need not detail return values but does so helpfully. The description covers the main use case and parameters adequately but could mention the optional 'email' parameter for rate limiting or the 'fields' parameter options. Still, it is largely complete for a single-resource fetcher.

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?

With 0% schema description coverage, the description must compensate. It thoroughly explains the main parameter 'taxon_id' with examples and accepted formats. However, it does not describe the 'email' and 'fields' parameters, leaving some ambiguity. The 'fields' default is 'all' but allowed values are unspecified. Thus it adds value but incompletely.

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 explicitly states the tool fetches a specific taxon by NCBI ID or scientific name, with concrete examples (e.g., 9606 for Homo sapiens). It clearly distinguishes from sibling tools like biothings_get_taxons (plural) which handles multiple taxa.

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 description clarifies when to use this tool (for a single taxon lookup) and implies that for multiple taxa one should use biothings_get_taxons. However, it does not explicitly state when not to use it or provide alternative tools, which would strengthen guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/longevity-genie/biothings-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server