Skip to main content
Glama

biothings_download_entrez_data_local

Download data from NCBI Entrez databases (e.g., nucleotide, protein) to a local file. Provide IDs, database, and format (fasta or gb) to save files on your machine.

Instructions

Download data from NCBI Entrez databases and save to local file.

        Same as download_entrez_data but saves the result to a local file instead of returning the content.
        This is useful for large downloads or when you want to persist the data.

        **Parameters:**
        - `ids` (List[str], required): A list of unique identifiers for the records to fetch
        - `db` (DB_LITERAL, required): The target NCBI Entrez database
        - `reftype` (Literal["fasta", "gb"], required): The desired format for the downloaded data
        - `output_path` (Optional[str]): Custom output path. If None, generates unique filename
        
        **Returns:**
        LocalFileResult containing:
        - `path`: Path to the saved file
        - `format`: File format used
        - `success`: Whether the operation succeeded
        - `error`: Error message if failed
        
        **Example Usage:**
        ```
        download_entrez_data_local(
            ids=["NM_000546.6"],
            db="nucleotide",
            reftype="fasta",
            output_path="tp53_sequence.fasta"
        )
        ```
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dbYes
idsYes
reftypeYes
output_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the behavior of saving to a local file, the output structure (LocalFileResult with path, format, success, error), and mentions that if output_path is None, a unique filename is generated. It does not mention potential side effects like overwriting files, but the unique filename generation mitigates that. The description adequately covers the core behavioral trait.

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 for description, parameters, returns, and example. It front-loads the core purpose and sibling differentiation in the first two sentences. Every sentence adds value, and the example code block is concise.

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?

Given the tool has 4 parameters and a sibling tool, the description covers all necessary aspects: core action, differentiation from sibling, parameter details, return structure, and usage example. No gaps remain for the agent to make an informed decision.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It does so excellently: each parameter is listed with type, requirement, and for db and reftype, the enum values are referenced. It explains the behavior of output_path (optional, custom path or unique filename). An example usage is provided that ties all parameters together.

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 action: 'Download data from NCBI Entrez databases and save to local file.' It immediately distinguishes itself from the sibling tool biothings_download_entrez_data by explaining that this version saves to a file instead of returning content.

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?

The description explicitly states when to use this tool: 'useful for large downloads or when you want to persist the data.' This implies when not to use it (when you want the content directly), effectively guiding the agent to choose between the two sibling tools.

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