Skip to main content
Glama

search_terms

Finds ontology terms by name, abbreviation, or synonym in any language, helping identify the correct term when the user's intended term is unclear.

Instructions

Find ontology terms by name, abbreviation or synonym, in any language. Use it when you are not sure which term the user means.

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": {
      "text": "<text>"
    },
    "name": "search_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 burden, yet it says nothing about matching behavior (exact vs partial), how many results come back, ranking, or what a result contains. It does disclose that matching spans name, abbreviation, synonym, and any language, but that is the only behavioral signal 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, no filler: the capability statement comes first and the usage cue second. Every word 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?

For a one-parameter search tool the description establishes what it does and when to reach for it, which is the core need. However, with no output schema the agent gets no indication of result shape or volume, and the single input parameter is only loosely characterized.

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 0% and the sole parameter is a bare 'text' string, so the description must compensate. It does add meaning by explaining that text can be a name, abbreviation, or synonym in any language, but gives no guidance on partial strings, casing, or format.

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 uses a specific verb ('Find') with a concrete resource ('ontology terms') and names the matching dimensions (name, abbreviation, synonym) plus language scope. It is clearly distinct from a detail-fetching tool like describe_term, though it never names a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use it when you are not sure which term the user means' gives an explicit triggering condition, which is strong guidance. It stops short of stating when not to use it or naming the alternative (e.g., describe_term once the term is known), so it is not a full 5.

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