Skip to main content
Glama

search_data

Read-onlyIdempotent

Full-text search across all askWheat resources (genes, germplasm, genotyping datasets, files).

Filters (exact values): database e.g. 'Ensembl Plants', 'Watkins Wheat Pangenome', 'CropSNPdb', 'GBIF genebank accessions'; entry_type e.g. 'Gene annotation', 'Germplasm', 'Genotyping Experiment', 'File'; species e.g. 'Triticum aestivum'. Returns total count, facet counts and the top hits with source URLs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
speciesNo
databaseNo
entry_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds valuable behavioral context beyond that: it discloses the return shape (total count, facet counts, top hits with source URLs), which matters since there is 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?

Front-loaded purpose sentence followed by a compact, clearly labeled filter list and a single return-value sentence. No filler, and the example values are the most actionable content placed where an agent will read it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter search tool with no output schema, the description covers the resource scope, filter vocabularies, and response shape. Remaining gaps are the meaning of the free-text query field and how limit/pagination behaves.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry parameter meaning and it largely does: database, entry_type and species are each given concrete example values, and the crucial hint that filters require exact values is spelled out. Only query and limit remain unexplained, which is a minor gap given the rest.

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 — full-text search — and scopes it to all askWheat resources, naming the resource families (genes, germplasm, genotyping datasets, files). It does not explicitly distinguish itself from siblings like search_literature or find_germplasm, leaving the boundary to be inferred.

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?

Implied usage is clear: a broad cross-resource search when the specific entity type is unknown. However, it never states when to prefer it over the narrower sibling tools, nor any conditions or prerequisites for use.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources