Skip to main content
Glama

search_data

Read-onlyIdempotent

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

Filters (exact values): database e.g. 'Ensembl Plants', 'Brassica Genome (brassicagenome.net)', 'GBIF genebank accessions'; entry_type e.g. 'Gene annotation', 'Germplasm', 'Genotyping Experiment', 'File'; species e.g. 'Brassica napus'. 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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond them by disclosing the return shape (total count, facet counts, top hits with source URLs), which matters for a search tool. It stops short of covering ranking, empty-result behavior, or how facets can feed follow-up queries (e.g. re-using a facet value as a filter).

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?

Front-loaded with the purpose in the first line, then filter semantics, then return shape, in a scannable order with no filler sentences. The semicolon-delimited filter list is compact. Slight cost: the parenthetical resource list and the filter examples both consume space without differentiating from siblings.

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?

With no output schema, the description correctly takes on the burden of describing return values, and it does so. Filters are covered with examples, which is what an agent needs to construct a valid call. What remains thin is the operational envelope: no hint about result limits, pagination beyond 'limit', whether facets can be re-fed as filters, or what a zero-hit response looks like.

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

Parameters4/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 the load, and it does for three of five parameters: it labels database, entry_type, and species with concrete example values such as 'Ensembl Plants' and 'Gene annotation'. It also flags that filters are exact-value matches, which is semantically important and absent from the schema. The required 'query' and 'limit' parameters are left unexplained, which is a minor but real gap.

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 with clear scope: 'Full-text search across all askBrassica resources (genes, germplasm, genotyping datasets, files)'. The enumerated resource types make the breadth explicit. It does not, however, distinguish itself from siblings like find_gene, find_germplasm, or search_literature, so an agent must infer that this is the broad catch-all search.

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 'across all ... resources', suggesting a broad entry-point search rather than a targeted lookup, but the description never says when this tool should be chosen over find_gene or find_germplasm. No prerequisites, exclusions, or alternatives are named, leaving the routing decision to inference from sibling names alone.

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