Skip to main content
Glama

Look up glossary terms

glossary_lookup
Read-onlyIdempotent

Look up CryptoDecentral glossary terms: plain-English definitions (40 words max) with related notes, see-also terms and primary sources. slug = exact match; q = match term, then alias, then definition text; neither = list terms (optionally by pillar). No match returns count 0. Education only, not financial advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "glossary_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional search text matched against term names first, then aliases, then definition text (case-insensitive), e.g. psbt or bip 174.
slugNoOptional exact glossary slug (the /glossary#anchor), e.g. gift-wrap-nip-59. Takes precedence over q.
limitNoMaximum results to return, 1 to 25 (default 10).
pillarNoOptional pillar filter: privacy, wallets, bitcoin, nostr, autonomi, deai or dex.

Output Schema

NameRequiredDescriptionDefault
siteYes
countYes
queryNo
totalNo
resultsYes
disclaimerYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description only needs to add context. It does: the 40-word definition cap, the exact shape of returned content, the "no match returns count 0" empty-result contract, and the education-only disclaimer all go beyond the structured fields.

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?

Three dense sentences, front-loaded with the resource and return shape, then the parameter modes, then the caveat. Semicolon-separated clauses carry a lot per word with no filler.

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?

An output schema exists, so return-structure explanation is optional, and the description nonetheless names the matching and empty-result behavior an agent needs. Only the limit/pagination interaction with the listing mode is unaddressed, a minor gap for a zero-required-parameter read tool.

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 the schema already documents q's match order, slug's precedence, the 1-25 limit range, and the pillar enum. The description restates the q/slug matching semantics and adds only the "neither = list" behavior, which is marginal value over the schema — the baseline 3 applies.

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?

States a specific verb and resource ("Look up CryptoDecentral glossary terms") and immediately characterizes the payload: plain-English definitions capped at 40 words plus related notes, see-also terms and primary sources. That is enough to distinguish it from siblings like get_note or search_content without opening a schema.

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?

Enumerates the three operating modes explicitly: slug for exact match, q for term-then-alias-then-definition search, and neither for listing with an optional pillar filter, including slug's precedence over q. It stops short of naming an alternative tool or a when-not-to-use condition, but the mode coverage is clear enough to route an agent correctly.

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