Skip to main content
Glama

get_bioproject

Retrieve detailed information about a specific NMDC BioProject using its accession ID to explore biological data collections.

Instructions

Get detailed information about a specific BioProject from NMDC. BioProjects are collections of biological data related to a single initiative.

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": {
      "accession": "<accession>"
    },
    "name": "get_bioproject"
  }
}

Input Schema

NameRequiredDescriptionDefault
accessionYesBioProject accession ID (e.g., PRJCA000001)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it discloses very little: 'detailed information' is unspecified, with no indication of what fields come back, how missing/invalid accessions are handled, or whether responses are cached or rate limited. Only the read-only nature is implied by 'Get', not stated.

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?

Two short sentences with the action front-loaded and no filler. The second sentence is short and earns some place by grounding the resource term, though it is definitional rather than operational.

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?

A read-only single-parameter lookup with 100% schema coverage and no output schema is a low-complexity case, and the description covers purpose and resource scope adequately. The missing piece is any hint about what 'detailed information' comprises, which would help an agent decide whether this call answers its question.

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?

The single parameter is fully documented in the schema, including an example format (PRJCA000001), so the schema does the heavy lifting and the baseline of 3 applies. The description adds no format, validation, or casing guidance beyond what the schema already provides.

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?

States a specific verb and resource: 'Get detailed information about a specific BioProject'. The second sentence defines what a BioProject is, which helps distinguish it from get_biosample and the search_* siblings by resource domain, though it never explicitly contrasts with them.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives such as search_nmdc_data or get_biosample, nor any stated precondition (e.g., 'use when you already have an accession'). The single required accession param implies a lookup-after-search pattern, but that inference is left entirely to the agent.

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