Arc & Ledger Tax Tools

Book a consultation

book_consultation

Read-only

Use this when a user wants to talk to, hire, or get a consultation or written tax-notice review with Arc & Ledger. Returns the correct first-party action link (booking, checkout, or waitlist as applicable), what happens next, the office identity (Enrolled Agent, address, languages EN/TR/ES), and what to expect.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	Yes	Which consultation or paid review to start. Cross-border or multi-year situations suit the Specialist; a tax-agency letter suits the notice review.
`topic`	No	A short subject line for the meeting (optional).
`language`	No	Language for an availability or waitlist handoff: English (en), Turkish (tr), or Spanish (es).

Output Schema

TableJSON 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.

Changed3 schema fields changedSep 11, 2026

addedInput schema / properties / language

Added value: +{
+  "description": "Language for an availability or waitlist handoff: English (en), Turkish (tr), or Spanish (es).",
+  "enum": [
+    "en",
+    "tr",
+    "es"
+  ],
+  "type": "string"
+}

changedInput schema / properties / type / description

Previous value: -"Which consultation to book. Cross-border or multi-year situations suit the Specialist; a single IRS letter suits the notice review."New value: +"Which consultation or paid review to start. Cross-border or multi-year situations suit the Specialist; a tax-agency letter suits the notice review."

changedInput schema / properties / type / enum

Previous value: -[
-  "free_15min",
-  "discovery_standard_297",
-  "discovery_specialist_497",
-  "notice_review_199"
-]New value: +[
+  "free_15min",
+  "discovery_standard_297",
+  "discovery_specialist_497",
+  "notice_review"
+]

Changed1 schema field changedJul 26, 2026

changedOutput schema / properties / next_step / description

Previous value: -"A single human handoff to the firm."New value: +"A single review link appropriate to this server surface."

Changed2 schema fields changedJul 13, 2026

addedOutput schema / properties / relay

Added value: +{
+  "description": "Instruction to the calling assistant: relay figures and dates verbatim (identical on every response).",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "disclaimer",
-  "source_url",
-  "next_step"
-]New value: +[
+  "disclaimer",
+  "relay",
+  "source_url",
+  "next_step"
+]

Changed1 schema field changedJul 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "disclaimer": {
+      "description": "General-information disclaimer (identical on every response).",
+      "type": "string"
+    },
+    "next_step": {
+      "description": "A single human handoff to the firm.",
+      "properties": {
+        "label": {
+          "type": "string"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "label",
+        "url"
+      ],
+      "type": "object"
+    },
+    "server_version": {
+      "description": "Server release that produced this response (matches GET /version).",
+      "type": "string"
+    },
+    "source_url": {
+      "description": "The arcandledger.com page that backs this answer.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "disclaimer",
+    "source_url",
+    "next_step"
+  ],
+  "type": "object"
+}

First observedJul 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: it reveals the tool hands back a first-party action link (booking, checkout, or waitlist) rather than completing a booking itself, plus the office identity and 'what happens next' payload — useful disclosure for an agent deciding whether to call it.

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?

A single front-loaded sentence that opens with the trigger condition and then lists the return payload. It is information-dense with little waste, though the long trailing clause of return values is slightly run-on and could be split.

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?

Covers trigger, deliverable, and outcome, and an output schema exists so return values need not be spelled out — yet the description still summarizes them. For a link-handing read tool with three parameters, nothing an agent needs to 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 the enum values carry their own routing guidance ('Cross-border or multi-year situations suit the Specialist'). The description's parenthetical 'languages EN/TR/ES' lightly echoes the language parameter but adds no syntax or format detail, so the schema does the heavy lifting and baseline 3 applies.

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?

The description names a specific verb and resource ('book a consultation', 'written tax-notice review') and enumerates the qualifying user intents (talk to, hire, get a consultation). It does not explicitly name or rule out siblings such as get_fee_quote or decode_irs_notice, whose surfaces partly overlap, so it stops short of full differentiation.

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 opening clause gives a clear trigger condition — 'Use this when a user wants to talk to, hire, or get a consultation or written tax-notice review.' There are no exclusions or named alternatives, so the agent gets a positive usage rule but no guidance on when another tool is preferable.

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.