Skip to main content
Glama

Glossary definition

get_term
Read-onlyIdempotent

Returns Advisorn's definition of a term (e.g. source-of-funds, kyt, peel-chain, issuer-freeze, party-appointed-expert, mica, travel-rule, carf, fadp) with explanation, related questions and page link.

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": {
      "id": "<id>"
    },
    "name": "get_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTerm id from search or list_topics, e.g. peel-chain.
langNoLanguage of the answer: en, it, de or fr.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds value by declaring the shape of the result: explanation, related questions, and a page link — important since no output schema exists. It says nothing about behavior for an unrecognized id or whether lang changes fallback behavior, which keeps it short of a 5.

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?

One front-loaded sentence with the resource named first and the payload after it — no redundant restatement of the tool name. The nine-item parenthetical of example slugs is somewhat long for a definition, though it does help an agent recognize the id vocabulary.

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 two-parameter, read-only lookup with annotations and no output schema, the description covers purpose and result composition sufficiently to make a correct call. The missing piece is how ids are sourced and how this differs from get_answer, which the description never bridges.

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 100%, so both id and lang are fully documented in the schema itself, including the enum and default. The description only echoes example ids already present in the schema, adding no new meaning; baseline 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 and resource ('Returns Advisorn's definition of a term') and goes further by listing the payload (explanation, related questions, page link). It does not distinguish itself from siblings such as get_answer or about_advisorn, so an agent must infer that this is a glossary lookup rather than a Q&A or metadata call.

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?

Usage is only implied by the phrase 'definition of a term' plus the slug examples; there is no explicit when-to-use statement, no exclusion against get_answer/search, and no note that an id must first be obtained (that hint lives only in the schema). Adequate but leaves routing to inference.

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