Skip to main content
Glama

get_nmdc_data_overview

Retrieve an overview of all NMDC data resources, including categories, databases, and record counts, to determine what microbiology data is available for exploration.

Instructions

Get an overview of all data resources available on the NMDC platform. Returns information about each data category, the databases within them, and their record counts. Use this to understand what data is available.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_nmdc_data_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does disclose the shape of the response (per-category info, databases within them, record counts) and implies a read-only, aggregate operation. It does not mention cost, size of the response, or that counts may be approximate — relevant for an 'all resources' call.

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?

Three short sentences, front-loaded with the primary action and followed by the return contents and use case. 'What data is available' partially echoes 'data resources available,' but the redundancy is minor.

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?

For a zero-parameter overview tool with no output schema, the description adequately covers what the tool does and what it returns. The only missing piece is any note on response size or follow-up tools to call once a category is identified.

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?

The tool takes no parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate beyond confirming the call is unfiltered and global.

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 an overview of all data resources available on the NMDC platform.' The scope ('all data resources') plus the enumerated return contents (categories, databases, record counts) clearly distinguish it from the search_* siblings, which target specific record types.

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?

'Use this to understand what data is available' gives an implied orientation/discovery use case, which is reasonable guidance. However, it offers no explicit when-not guidance and does not name any alternative for drilling into a specific category once the agent sees the overview.

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