Skip to main content
Glama

search

Find species and organisms across comparative biology catalogs by semantic or keyword query, with filters for entity type and result limits.

Instructions

Unified cross-catalog semantic or keyword search across species and individual organisms in the Biologist comparative biology manifold.

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": {
      "q": "<q>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query text (e.g. 'deep-sea bioluminescent anglerfish', 'desert nocturnal burrowing rodent')
modeNoSearch mode: semantic (pgvector cosine similarity), keyword (text matching), or autoauto
limitNoMaximum number of results to return (1-100)
target_typeNoFilter search results by entity type: all, species, or organismall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not say whether the operation is read-only, how results are ranked or ordered, whether there is pagination beyond limit, or what the response contains — all material for a search tool with zero annotation coverage.

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?

A single front-loaded sentence with no redundant clauses. The trailing 'in the Biologist comparative biology manifold' is somewhat decorative, but nothing is wasted or buried.

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

Completeness2/5

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

With no annotations and no output schema, the definition should compensate by describing the result shape, ordering, and pagination behavior; it says none of these. For a four-parameter search entry point the description leaves the agent guessing about what comes back.

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 all four parameters (q, mode, limit, target_type) are already documented with enums and defaults. The description's mention of semantic/keyword and species/organism mirrors the schema without adding format, syntax, or query-construction guidance, so baseline 3 applies.

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 names a specific verb (search) plus its scope: species and individual organisms, over a cross-catalog index, using semantic or keyword matching. An agent can tell what the tool retrieves, though the phrase 'Biologist comparative biology manifold' adds jargon rather than precision about the corpus.

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?

There is no when-to-use guidance, no statement of when to prefer this over entity-specific retrieval tools like get_species or get_organism, and no advice on choosing semantic vs keyword vs auto. 'Unified' hints that it spans catalogs but does not route the agent between alternatives.

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