Skip to main content
Glama

biothings_download_entrez_data

Retrieve biological sequence or record data from NCBI Entrez databases by providing IDs, database name, and format (FASTA or GenBank).

Instructions

Download data from NCBI Entrez databases using Bio.Entrez.

        Downloads data records from specified NCBI Entrez databases. This tool is designed to be called 
        by automated agents (like LLMs) or other services.

        **Critical Configuration:**
        The server hosting this API *must* have the `ENTREZ_EMAIL` environment variable set
        to a valid email address. NCBI requires this for Entrez queries to monitor usage
        and prevent abuse. Without it, NCBI may block requests.

        **Parameters:**
        - `ids` (List[str], required): A list of unique identifiers for the records to fetch
          from the specified Entrez database. Example: `["NM_000546.6", "AY123456.1"]`
        - `db` (DB_LITERAL, required): The target NCBI Entrez database.
          Common choices for sequences: 'nucleotide', 'protein'.
          Other examples: 'gene', 'pubmed', 'taxonomy'.
          Ensure the `ids` provided are appropriate for the selected `db`.
        - `reftype` (Literal["fasta", "gb"], required): The desired format for the
          downloaded data.
            - "fasta": Returns data in FASTA format.
            - "gb": Returns data in GenBank format.
          Ensure the chosen `reftype` is compatible with the selected `db`.

        **Returns:**
        On success: Returns the downloaded data as a single raw string with the
        data fetched from Entrez in the specified `reftype`.
        
        **Example Usage:**
        To fetch the FASTA sequence for human TP53 mRNA (NM_000546.6):
        ```
        download_entrez_data(
            ids=["NM_000546.6"],
            db="nucleotide",
            reftype="fasta"
        )
        ```
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dbYes
idsYes
reftypeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the need for ENV variable, return format (raw string), and mentions NCBI blocking possibility. It lacks details on rate limits, error handling, or empty results.

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

Conciseness3/5

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

The description is long but well-structured with sections (Critical Configuration, Parameters, Returns, Example). It contains some redundancy (e.g., 'This tool is designed to be called...'). Could be more concise without losing clarity.

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 tool has 3 parameters, no annotations, and an output schema (though not provided), the description covers essential aspects: parameter details, configuration, return value type, and an example. It is complete enough for an agent to use correctly.

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

Parameters4/5

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

Schema coverage is 0% (no descriptions in schema). The description compensates with detailed explanations: ids (list with example), db (enum with common choices and caution), reftype (two literals with format descriptions). This adds significant meaning 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?

The description clearly states the tool downloads data from NCBI Entrez databases using Bio.Entrez. It uses specific verb (download) and resource (Entrez databases). However, it does not differentiate from the sibling tool 'biothings_download_entrez_data_local'.

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?

The description provides critical configuration requirements (ENTREZ_EMAIL) and an example, but does not explicitly state when to use this tool versus alternatives (e.g., local version). No exclusions are mentioned.

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