Skip to main content
Glama

search_gcm

Search the Global Catalogue of Microorganisms (GCM) for microbial strains in worldwide culture collections by keyword, strain, or species name.

Instructions

Search the Global Catalogue of Microorganisms (GCM) on NMDC. The GCM provides information about microbial strains held in culture collections worldwide.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-indexed), default: 1
sizeNoNumber of results per page, default: 20
keywordNoSearch keyword (e.g., strain name, species name)

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 supplied, so the description carries the full behavioral burden, yet it says nothing about pagination behavior, result ordering, what an empty keyword returns, or what the response looks like. The read-only nature is inferable from 'Search' but never confirmed, and the notable fact that all three parameters are optional is not addressed.

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 verb and resource, with no wasted wording. The second sentence earns its place by explaining what GCM data is, though it stops short of operational guidance.

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 three-optional-parameter search tool with full schema coverage and no output schema, the description is minimally adequate. It omits what results contain and how an empty or broad keyword is handled, which an agent would need to call it confidently.

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 directly in the schema, so the baseline is 3. The description adds no extra semantics about keyword matching behavior (e.g., partial vs exact, multi-word handling) that the schema does not already cover.

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 ('Search') and a specific resource ('Global Catalogue of Microorganisms (GCM) on NMDC'), and the second sentence clarifies what that resource contains (microbial strains in culture collections). It does not differentiate itself from nearby siblings such as search_microbial_catalog or search_microbial_dictionary, leaving overlap for the agent to resolve.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. At best the second sentence implies the tool is relevant when looking for culture-collection strain records, which is indirect rather than stated.

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