Skip to main content
Glama

Arc & Ledger Tax Reference

by com.arcandledger

Explain a tax document

explain_tax_document
Read-only

Use when a user names a US tax form or information document and wants to understand its purpose, common fields, or usual return treatment. Do not request or accept the document itself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
briefNoSet true for a shorter answer: skips the box-by-box guide and the pre-filing checklist.
documentYesThe tax form or document name as printed on it, e.g. "W-2", "1099-K", "1099-NEC", "Schedule K-1 (Form 1065)", "1042-S", "1098-T", "SSA-1099", "1095-A", "W-9".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
relayYesInstruction to the calling assistant: relay figures and dates verbatim (identical on every response).
next_stepYesA single review link appropriate to this server surface.
disclaimerYesGeneral-information disclaimer (identical on every response).
source_urlYesOfficial IRS or FinCEN authority to review before relying on the result.
server_versionNoServer release that produced this response (matches GET /version).

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds critical behavioral rule: 'Do not request or accept the document itself.' This clarifies the tool only works on form names, not the documents themselves. No contradiction with annotations.

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?

Two sentences, no filler. First sentence front-loads purpose and usage condition. Second sentence adds a key behavioral constraint. Every word earns its place.

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 straightforward explainer tool with full schema coverage and an output schema (implied), the description provides all necessary context: what it explains, when to use, and what not to do. No gaps.

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?

Input schema has 100% description coverage for both parameters. Description does not add new parameter-specific meaning beyond what the schema provides. Meets baseline expectation.

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?

Description explicitly states the action ('explain') and resource ('US tax form or information document') and its purpose ('understand its purpose, common fields, or usual return treatment'). Sibling tools have distinct purposes (e.g., check obligations, decode notices), so no confusion.

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?

Description clearly indicates when to use ('when a user names a US tax form ... and wants to understand'). Does not provide explicit when-not-to-use or alternatives, but sibling tools are sufficiently different that context implies correct usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Arc & Ledger Tax Reference toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool addresses a distinct tax topic or action, such as screening obligations, checking eligibility, estimating amounts, or explaining documents. There is no overlap in purpose, making it easy for an agent to select the correct tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun or verb_phrase pattern (e.g., check_*, estimate_*, explain_*, decode_*, deadline_calendar). The naming is predictable and clear across the set.

Tool Count5/5

With 13 tools, the server covers a broad range of tax reference needs without being overwhelming. Each tool has a clear purpose and the count is well-suited for the domain.

Completeness4/5

The tools cover common tax reference tasks like screening obligations, estimating penalties, explaining forms, and checking deadlines. A minor gap is the lack of a general tax liability estimator, but overall the set is comprehensive for its stated purpose.

Resources