Skip to main content
Glama

get_analysis_tools

Retrieve available bioinformatics analysis tools on the NMDC platform to choose options for microbiology data analysis.

Instructions

Get a list of analysis tools available on the NMDC platform. These tools can be used for bioinformatics analysis of microbiology data.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. 'Get a list' implies a read-only catalog lookup, but the description does not disclose the return structure, whether the list is static or dynamic, pagination behavior, or any authentication requirements, leaving meaningful behavioral gaps for an unannotated tool.

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 is front-loaded with the core action. The second sentence adds relevant domain context without unnecessary wording, though it is somewhat generic.

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?

The tool is conceptually simple with no parameters and no output schema, so a short description is reasonable. However, because there is no output schema, the description should ideally explain what each listed analysis tool includes and how the returned tools are meant to be used, rather than only saying they exist for bioinformatics analysis.

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 has zero parameters, so the baseline is 4 under the scoring rules. The description correctly adds no parameter meaning because there are no parameters to explain.

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: 'Get a list of analysis tools available on the NMDC platform.' This clearly distinguishes it from the sibling data-search and metadata tools, though it does not explicitly name or contrast those alternatives.

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?

The sentence about bioinformatics analysis of microbiology data gives useful context for why an agent might call this tool, implying usage when available analysis capabilities are needed. However, it provides no explicit when-to-use guidance, exclusions, or routing against sibling tools such as search_nmdc_data.

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