Skip to main content
Glama

Get a glossary term

get_term
Read-onlyIdempotent

Get one glossary term by slug (e.g. "abstention-band"), by its id ("t-abstention-band"), by its page URL or by its name ("Abstention band", or an acronym in brackets such as "AUP"). Returns the definition, the canonical page, the chapters that use it and the other terms whose definitions mention 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": {
      "slug": "<slug>"
    },
    "name": "get_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesTerm slug, id, URL or name.

Output Schema

NameRequiredDescriptionDefault
urlYesCanonical page of the term.
slugYes
termYes
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).
chaptersYesChapters that use the term.
definitionYes
dataVersionYesBody of Knowledge version of the data.
glossaryUrlYesThe term in the glossary chapter.
mentionedInYesOther terms whose definitions mention this one (up to 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the operation read-only, idempotent, non-destructive, and closed-world. The description adds useful context by explaining the accepted identifier variants and summarizing the returned content, though it does not cover error behavior or ambiguity resolution.

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?

The definition is front-loaded and dense with useful detail. Every clause either specifies an accepted identifier format or states what the response contains; none of it is padding.

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?

With one required parameter, full schema description coverage, an output schema, and annotations covering safety and idempotency, the description supplies the remaining needed context: the range of acceptable identifiers and a summary of the returned glossary data.

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% and the schema already says the slug parameter accepts a slug, id, URL, or name. The description adds concrete examples such as 'abstention-band', 't-abstention-band', page URLs, and bracketed acronyms like 'AUP', giving more practical meaning than the schema alone.

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?

The description states a specific verb and resource: 'Get one glossary term.' It also makes clear this is a single-item lookup rather than a search, which distinguishes it naturally from sibling tools such as search_glossary.

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?

The accepted identifier forms imply that the tool should be used when an agent already has a slug, id, URL, or term name, but there is no explicit guidance on when to prefer search_glossary instead or on when not to use this tool.

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.