Skip to main content
Glama

search_data

Read-onlyIdempotent

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

Filters (exact values): database e.g. 'Ensembl Plants', 'Legume Information System', 'GBIF genebank accessions'; entry_type e.g. 'Gene annotation', 'Germplasm', 'Genotyping Experiment', 'File'; species e.g. 'Pisum sativum', 'Vicia faba', 'Glycine max'. 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.5/5.0
Behavior3/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 the safety profile is covered. The description adds genuinely useful context: it discloses the return payload (total count, facet counts, top hits with source URLs) and warns that filters match exact values rather than fuzzy text. It does not disclose result ordering, pagination, or rate/scale behavior for an open-world search.

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-loads the purpose in one sentence, then a compact filter list with inline examples, then the return summary. No filler. The filter block is slightly dense but every item earns its place.

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?

There is no output schema, and the description does give a brief but adequate return summary (counts, facets, hits with URLs). For an open-world, 5-parameter search tool with zero schema documentation, however, missing query syntax, result ranking, and how limit interacts with facets leaves real gaps.

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 explains three of five parameters (database, entry_type, species) with concrete example values and the crucial 'exact values' matching rule. It leaves 'query' semantics (free text vs boolean syntax) and 'limit' behavior (10 default per schema) unexplained.

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+resource ('Full-text search across all askPulse resources') and enumerates the resource families covered (genes, germplasm, genotyping datasets, files). It does not differentiate itself from sibling lookups such as find_gene or find_germplasm, so an agent must infer that this is the broad/exploratory entry point.

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 rather than stated: 'full-text search across ALL resources' hints at broad discovery, and the filter list hints at narrowing. There is no explicit 'use this instead of X when Y' guidance and no statement about when this tool is the wrong choice relative to the specialized sibling tools.

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