Skip to main content
Glama

Swarm Ecology register

search_glossary

Read-only

Returns up to eight glossary terms whose term or definition contains the query.

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_glossary"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesText to find in a term or definition.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: a hard cap of eight results and the fact that matching covers both the term and the definition rather than just the term name. It stops short of explaining ordering, case sensitivity, or what happens when more than eight terms match.

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?

One sentence with no filler, and the most decision-relevant facts (result cap, match scope) are stated up front. Nothing needs trimming.

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 one-parameter search tool with full schema coverage and no output schema, the definition covers purpose, match scope, and result limit adequately. Minor gaps remain around result ordering and truncation signaling when more than eight terms match, but nothing essential is missing to invoke it correctly.

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?

With a single parameter and 100% schema description coverage, the schema already defines query as 'Text to find in a term or definition.' The description restates that same semantics without adding format, case, or stemming guidance, so the baseline of 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?

States a specific verb+resource (returns glossary terms) and narrows the matching to term or definition, so the agent knows exactly what is retrieved. It does not differentiate itself from the siblings search_library or lookup_case, which is the only reason it falls short of a 5.

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?

Appropriate usage is implied by the substring-match semantics: use it when you have partial text to find in a term or definition. There is no explicit when-to-use, when-not, or pointer to lookup_case for exact-name resolution, so the agent must infer the boundary.

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