Skip to main content
Glama

search_fungi

Search fungi data on NMDC by keyword, including fungal names, genome records, type specimens, and related information, with paginated results.

Instructions

Search fungi microorganism data on NMDC. Includes fungal names, genome data, type specimens, and related information.

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

Input Schema

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

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 states that the tool searches fungal data and lists content categories, but does not describe result behavior, pagination, ordering, whether an empty keyword returns all records, or any limitations. For a search endpoint with no annotation coverage, this is a meaningful 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?

The description is short, front-loaded, and has no wasted preamble. The phrase 'related information' is slightly vague, but overall the structure is efficient and easy to parse.

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, the description covers the basic data scope and is consistent with the schema. However, with no output schema and no annotations, it should say more about what a result contains or how pagination and result limits behave.

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%, so the input schema already documents page, size, and keyword. The description does not add parameter semantics beyond the schema; its mention of fungal names and species largely mirrors the keyword example already present in the schema.

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 and resource: search fungi microorganism data on NMDC, and adds that results include fungal names, genome data, and type specimens. It is clear what the tool does, though it does not explicitly distinguish itself from nearby search tools such as search_genome or search_microbial_catalog.

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 fungal-specific scope, but the description provides no explicit when-to-use or when-not-to-use guidance relative to sibling tools. An agent can infer that this is for fungi queries, but there are no stated alternatives or exclusions.

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