Arc & Ledger Tax Tools

Get an itemized tax return quote

get_itemized_quote

Read-only

Use this when a user wants to know what Arc & Ledger would charge to prepare their tax return and can describe their situation: the type of return, number of states, foreign accounts, K-1s, rental properties, crypto activity, and whether prior years are unfiled. Returns the exact published line items and a total, computed by the same engine as the firm's quote page. For a broad price range by service category without these details, use get_fee_quote instead.

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": {
      "filing": "<filing>"
    },
    "name": "get_itemized_quote"
  }
}

Input Schema

Name	Required	Description	Default
`crypto`	No	Crypto activity in the year: none, some (up to 50 transactions), or heavy (50 to 500 transactions).	none
`filing`	Yes	The main return: w2 (individual, wage income), self_employed (Schedule C or single-member LLC), scorp_partnership (Form 1120-S or 1065), ccorp (Form 1120), or foreign_llc (foreign-owned LLC, Form 5472 with pro-forma 1120).
`states`	No	Number of states with a filing requirement. One state is included in the base return.
`k1_count`	No	Number of Schedule K-1s the taxpayer receives.
`clean_books`	No	Business filers only: true if the books are reconciled and current, false if they need cleanup first.
`behind_years`	No	True if one or more prior-year returns are unfiled.
`multi_entity`	No	True if more than one entity, or a cross-border group, is involved.
`rental_count`	No	Number of rental properties reported on Schedule E.
`foreign_accounts`	No	True if the taxpayer has foreign bank or brokerage accounts over the FBAR reporting threshold.

Output Schema

Name	Required	Description
`relay`	Yes	Instruction to the calling assistant: relay figures and dates verbatim (identical on every response).
`next_step`	Yes	A single review link appropriate to this server surface.
`disclaimer`	Yes	General-information disclaimer (identical on every response).
`source_url`	Yes	The arcandledger.com page that backs this answer.
`server_version`	No	Server release that produced this response (matches GET /version).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare read-only, non-destructive, closed-world behavior, and an output schema exists. The description adds meaningful context beyond that: the numbers come from the same engine as the firm's public quote page, so results are authoritative and reproducible rather than an approximation, and the response is exact line items plus a total.

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: the first front-loads the trigger and the required inputs, the second states the output and the routing alternative. No filler, and the fallback tool is named last where an agent would look after confirming this isn't the right fit.

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 read-only calculator with full schema coverage and a declared output schema, the description covers the trigger, the required informational inputs, the nature of the result, and the alternative tool. Nothing an agent needs in order to select and call it correctly is missing.

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% and every parameter (including enum meanings and bounds) is documented in the schema. The description only restates the input categories at a high level and adds no pricing or interpretation semantics beyond what the schema already supplies, so 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?

The description states a specific verb and resource — computing an itemized quote of what the firm would charge to prepare a return — and lists the inputs that drive it. It explicitly contrasts itself with get_fee_quote ('broad price range by service category'), so an agent can route between the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the triggering condition ('when a user wants to know what Arc & Ledger would charge and can describe their situation') and the exclusion condition ('without these details'), directing that case to get_fee_quote. Both the when and the when-not are explicit, along with the alternative.

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 Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.