Skip to main content
Glama

glossary_get

One glossary with its terms.

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": {
      "glossary_id": "<glossary_id>"
    },
    "name": "glossary_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
glossary_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full burden of behavioral disclosure. It adds one useful fact — the response bundles the glossary's terms — but says nothing about read-only semantics, what happens with an unknown or inaccessible glossary_id, or whether the term set is paginated or truncated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is short with zero padding, but it is a sentence fragment rather than a front-loaded statement of action plus scope. Brevity here comes from under-specification rather than disciplined editing.

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?

This is a low-complexity single-parameter read with no output schema, so a terse description can suffice; the note that terms are included is helpful. Still, with no annotations and no parameter documentation anywhere, the definition leaves the agent guessing about identifier semantics and failure behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single required parameter glossary_id is undocumented. The description never references the identifier, so the agent gets no meaning (format, source, whether it is a numeric id or slug) beyond the bare string type in the schema.

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

Purpose3/5

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

The fragment 'One glossary with its terms' conveys the resource (a single glossary) and hints at the return payload (its terms), which separates it loosely from the sibling glossary_list. However, there is no verb and no explicit statement of what operation is performed (fetch/read), so an agent must infer it from the name glossary_get.

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?

The word 'One' implicitly contrasts with a list-style sibling, but the description never states when to use this tool versus glossary_list or glossary_terms_add. There are no exclusions, prerequisites, or alternative routing hints of any kind.

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