Skip to main content
Glama

Search the glossary

search_glossary
Read-onlyIdempotent

Search the canonical terms of AI governance engineering (definitions from the Body of Knowledge glossary, chapter 09). Matches term names, acronyms and definition text; every query word must match. Returns term slugs for get_term, definitions, the canonical page URL of each term and the chapters that use it.

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
limitNoMaximum number of terms to return.
queryYesWords to look for, e.g. "abstention band", "FRIA", "model card".

Output Schema

NameRequiredDescriptionDefault
queryYes
totalYesNumber of matching terms (before the limit).
noticeYesIllustrative, not legal advice and not a claim of conformity.
sourceYesCanonical URL of the page this answer comes from; cite it.
datasetYesURL of the open-data document the answer was read from.
licenseYesLicence of the data (CC BY 4.0, attribution required).
resultsYes
dataVersionYesBody of Knowledge version of the data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world behavior, so the description's job is to add something else, which it does: the conjunction/AND matching semantics and the exact fields returned (slugs, definitions, canonical URL, using chapters). It does not mention the default or maximum result count that governs truncation.

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?

Three sentences, densely packed and front-loaded with the scope before the matching rule and return fields. The final clause enumerating return values is partly redundant with the existing output schema, which is the only slack in an otherwise tight definition.

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

Completeness5/5

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

For a two-parameter read-only search with rich annotations, full schema coverage and an output schema, the description supplies everything missing from structured fields: search scope, AND-match behavior, and the hand-off to get_term. An agent can call this correctly without opening any other field.

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 100%, so a 3 baseline applies, but the description genuinely adds meaning beyond the schema by specifying which fields are searched (term names, acronyms, definition text) rather than just 'words to look for'. The limit parameter is left entirely to the schema, which is acceptable given full coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (Search) and a precise resource scoped to canonical AI-governance terms from the Body of Knowledge glossary, chapter 09. That scope implicitly separates it from the broader search_bok, and the mention of returning slugs 'for get_term' signals that it is a discovery tool whose companion is get_term, not a fetch tool.

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?

Clearly frames the tool as a lookup pass whose output feeds get_term, which gives an agent a usable workflow. It also states the matching rule ('every query word must match'), which directly shapes how an agent should phrase a query. It stops short of explicitly excluding alternatives such as search_bok for non-glossary content.

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.