Skip to main content
Glama

search_metagenome

Search NMDC metagenome records by keyword to find environmental and host-associated microbiome sequences, with paginated results for browsing.

Instructions

Search metagenome data on NMDC. Metagenomic data includes environmental and host-associated microbiome sequences.

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": "search_metagenome"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-indexed), default: 1
sizeNoNumber of results per page, default: 20
keywordNoSearch keyword (e.g., environment type, organism)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 behavioral burden. It discloses nothing about what is returned (record shape, counts), whether the search is keyword-matched against which fields, authentication or rate-limit constraints, or how pagination behaves beyond the schema defaults. For a search tool with zero annotation coverage this is a substantial gap.

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, front-loaded with the action and resource, with zero filler. The second sentence earns its place by defining scope, though it could have been spent on routing guidance instead.

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?

With three fully documented optional parameters and no output schema, the core invocation is covered. But absent annotations and an output schema, the description should compensate by describing return content and result behavior, which it does not.

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?

Schema description coverage is 100%, with page, size, and keyword each documented inline including defaults and bounds, so the schema does the heavy lifting. The description adds no parameter-level meaning, such as which fields the keyword matches or how pagination interacts with result ordering, which is the baseline expectation here.

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 gives a specific verb+resource pair ("Search metagenome data on NMDC") and the second sentence scopes the domain to environmental and host-associated microbiome sequences, which implicitly separates it from siblings like search_genome or search_virus. It stops short of naming any sibling explicitly, so an agent must infer the boundary from subject matter alone.

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 implied by the resource name and the clarifying sentence about what counts as metagenomic data, which helps an agent decide relevance. However, there is no explicit when-to-use, when-not-to-use, or pointer to an alternative such as search_nmdc_data for broader queries, leaving the routing decision to inference.

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