Skip to main content
Glama

search_ncov_variation

Search SARS-CoV-2 genomic variation, mutation, and epidemiological data on NMDC by keyword, with paginated results for exploring novel coronavirus variation records.

Instructions

Search SARS-CoV-2 (novel coronavirus) variation data on NMDC. Includes genomic variations, mutations, and related epidemiological 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": "search_ncov_variation"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-indexed), default: 1
sizeNoNumber of results per page, default: 20
keywordNoSearch keyword

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 burden of behavioral disclosure. It only states the data domain and included data types; it does not explain result ordering, pagination behavior beyond schema fields, authentication needs, limits, or what the search returns. This is a significant gap for a search tool with no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two concise sentences with no filler, and the resource scope is front-loaded. Each sentence contributes useful information about the domain and included data types.

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 simple three-parameter search tool with full schema coverage, the description identifies the data domain and categories of variation data. However, with no annotations and no output schema, it leaves result format, result behavior, and practical search expectations unstated, so completeness is only adequate.

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%, and the schema already documents page, size, and keyword with defaults and bounds. The description adds no additional meaning about keyword scope, search syntax, or how page and size interact with results.

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 and resource: search SARS-CoV-2 variation data on NMDC, and it enumerates genomic variations, mutations, and related epidemiological data. It clearly scopes the resource narrower than generic virus or pathogen search, though it does not explicitly name a sibling alternative.

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?

The description implies a search use case but gives no when-to-use guidance, exclusions, or routing to alternatives such as search_virus, search_pathogen, or search_nmdc_data. An agent must infer the appropriate context from the domain wording alone.

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