Skip to main content
Glama

get_metadata_standards

Retrieve NMDC metadata standards, schemas, and compliance requirements to understand data submission rules and prepare compliant submissions.

Instructions

Get metadata standards information from NMDC. Includes information about data submission standards, metadata schemas, and compliance requirements.

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

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?

With no annotations supplied, the description carries the full disclosure burden. It implicitly signals a read-only reference lookup ("Get ... information"), which is low-risk with zero parameters, but it does not state whether the returned standards are static documentation, versioned, or scoped to a particular NMDC release, nor what shape the response takes.

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 resource and source front-loaded and the content categories immediately following. Nothing is wasted, though "information" is repeated and the second sentence could carry more specificity.

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 reference tool with no output schema, the description does enough: it names the source system and the three categories of content returned. It stops short of describing the return structure or how the standards relate to the other NMDC data tools, which would help an agent decide when this is the right resource.

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 there is nothing for the description to disambiguate beyond confirming that no inputs are needed. Baseline of 4 applies for a zero-parameter 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 uses a specific verb+resource ("Get metadata standards information from NMDC") and enumerates the content categories: submission standards, metadata schemas, and compliance requirements. That distinguishes it from the search_*/get_* data-retrieval siblings, which return records rather than documentation, though it never explicitly contrasts itself 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 Guidelines3/5

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

Usage is only implied by the content enumeration: an agent can infer it should call this when it needs to know how to submit data or interpret NMDC schemas. There is no explicit when-to-use statement, no prerequisites, and no named alternative to consider instead.

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