Skip to main content
Glama

explain_term

Read-only

Plain-language definition of an accounting, tax, or compliance term (e.g. "accrual", "GSTR-3B", "input tax credit", "P&L", "reconciliation", "BAS", "1099"). Resolves by exact name, alias, or fuzzy match against a curated glossary scoped to bookkeeping plus the IN/UK/AU/US/CA regimes HelloBooks serves; returns the definition, related terms, or the closest suggestions. Definitions are general guidance — confirm specifics against the relevant authority.

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": {
      "term": "<term>"
    },
    "name": "explain_term"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesThe accounting/tax term to define, e.g. "accrual", "GSTR-3B", "input tax credit", "P&L".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations establish readOnlyHint=true and openWorldHint=false, but the description adds genuinely new behavior: the match strategy (exact name, alias, fuzzy), the curated closed corpus, the degraded response when no match is found ("closest suggestions"), and a correctness caveat that definitions are guidance rather than authority. It does not cap request rate or describe format/length of the returned definition, but for a read-only lookup the safety profile is adequately covered.

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?

Front-loaded with the one-line purpose, then resolution behavior, then scope, then the caveat — a sensible order with no filler. The example list is long enough to be slightly redundant with the schema's examples, but every sentence carries information.

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?

For a single-parameter read-only lookup with no output schema and closed-world annotations, the description covers what it does, how input is matched, what comes back (definition, related terms, or suggestions), and the geographic limits of the corpus. An agent has everything needed to invoke it correctly and to interpret a miss.

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 description coverage is 100%, so the baseline is 3, and the description goes beyond it by explaining how the single `term` value is resolved — exact name, alias, or fuzzy match — which is interpretation semantics the schema does not encode. The repeated example terms partially duplicate the schema's own examples, which keeps this from a 5.

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+resource ("plain-language definition of an accounting, tax, or compliance term") and disambiguates with seven concrete example terms spanning bookkeeping and multi-country regimes. Nothing in the sibling list (analyze_*, list_*, estimate_*) overlaps with a glossary lookup, so the tool is clearly separable without opening its 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?

The description makes the use case unambiguous — an agent knows to call this whenever a term's meaning is needed rather than guessing — and the jurisdiction scoping (IN/UK/AU/US/CA) tells the caller when the glossary will actually cover a term. It stops short of naming a sibling as the alternative for out-of-scope or non-glossary lookups (e.g. feature_search, list_articles), so no explicit exclusion or fallback routing is given.

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