Skip to main content
Glama

Explain a word

explain_term
Read-only

A plain-English meaning of a word used on the site: digital signature, invoice, Federated Computing, confidential hardware, attestation, receipt, AI agent, MCP. Without a word, lists them all.

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": "explain_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
termNoThe word to explain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered. The description adds real context beyond that: the vocabulary is a fixed, site-specific glossary (shown by the enumerated examples) and calling with no term returns the full list rather than erroring.

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 sentence plus a short clause, front-loaded with the core purpose and followed by behavior for the no-arg case. The list of example terms is somewhat long but efficiently communicates the closed 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 trivial single-parameter read tool with no output schema, the description covers purpose, scope, and the optional-argument path. It leaves unspecified what happens for a term outside the glossary, which is a minor but real gap.

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 single parameter is self-describing, so baseline is 3. The description earns one more by explaining that the parameter is optional and what happens when it is omitted, which the schema alone does not make obvious.

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 ('plain-English meaning of a word used on the site') and the example terms make the domain concrete. It doesn't explicitly differentiate itself from glossary-adjacent siblings like get_guide or get_overview, so it stops short of a 5.

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 no-argument branch ('Without a word, lists them all') is a genuinely useful routing hint, implying a discovery-then-lookup workflow. However, no sibling is named and there is no explicit when-not-to-use guidance against get_guide/get_overview.

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