Skip to main content
Glama

search_virus

Find virus sequences, genome annotations, and related pathogen data in NMDC by keyword, with paginated results for browsing.

Instructions

Search virus pathogen data on NMDC. Includes virus sequences, genome annotations, and related 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_virus"
  }
}

Input Schema

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

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?

With no annotations, the description carries the full behavioral burden, but it only implies a read-only search. It says nothing about pagination behavior, result limits, whether the search is exact or fuzzy, or what permissions or rate limits apply.

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 core action. The second sentence is mostly a restatement of scope but does add useful detail about the data types covered.

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 3-parameter search with no output schema, the description covers what is searched but leaves out result shape, matching semantics, and default behavior. It is adequate but thin given the absence of annotations.

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 coverage is 100%, so page, size, and keyword are already fully documented in the schema. The description adds no extra meaning about keyword matching or paging behavior, which is acceptable at baseline but not more.

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 and resource ('Search virus pathogen data on NMDC') and scopes the content to virus sequences and genome annotations, which separates it from sibling searches like search_fungi or search_tuberculosis. It does not, however, state how it differs from search_pathogen, which sounds like the closest overlap.

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 gives no when-to-use or when-not-to-use guidance and names no alternatives. An agent choosing between search_virus, search_pathogen, search_genome, and search_ncov_variation gets no routing signal beyond the word 'virus'.

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