Skip to main content
Glama

get_biosample

Retrieve detailed information about a specific NMDC BioSample by accession ID to identify its biological source material for sequencing studies.

Instructions

Get detailed information about a specific BioSample from NMDC. BioSamples are biological source materials used in sequencing.

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_biosample"
  }
}

Input Schema

NameRequiredDescriptionDefault
accessionYesBioSample accession ID (e.g., SAMC000001)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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 of behavioral disclosure. It implies a read-only lookup but does not state what 'detailed information' includes, whether authentication is required, how errors are handled, or what the response format looks like.

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?

The description is two short sentences and front-loads the core action and resource. The second sentence adds useful domain context about what a BioSample is, though it is not strictly necessary for invocation.

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

Completeness3/5

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

For a simple one-parameter retrieval tool, the description covers the essential purpose and resource. However, without annotations or an output schema, it could do more to explain what detailed information is returned and what an agent should expect from the response.

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 schema has 100% description coverage and explicitly documents the accession parameter with an example. The description adds no meaning beyond the schema for this single parameter, which is the expected baseline when the schema is fully documented.

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 states a specific verb and resource: retrieving detailed information about a specific BioSample from NMDC. It clearly distinguishes the resource from sibling retrieval tools like get_bioproject. However, it does not explicitly contrast itself with search_nmdc_data or other search tools, so it stops short of full 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 Guidelines2/5

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

The description implies that the tool is used when you have a specific BioSample accession and need details, but it gives no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives such as searching first versus retrieving directly by accession.

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