Arc & Ledger Tax Tools

Request 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. Consultation requests start with a written inquiry on the contact form; the firm does not offer free calls. Returns the correct first-party action link (inquiry form, checkout, or waitlist as applicable), what happens next, the office identity (Enrolled Agent, address, languages EN/TR/ES), and what to expect.

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": {
      "type": "<type>"
    },
    "name": "book_consultation"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	Which consultation or paid review to start. contact_form is the no-charge written inquiry that every general consultation request starts with. 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

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.

Changed2 schema fields changedOct 22, 2026

changedInput schema / properties / type / description

Previous 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."New value: +"Which consultation or paid review to start. contact_form is the no-charge written inquiry that every general consultation request starts with. 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"
-]New value: +[
+  "contact_form",
+  "discovery_standard_297",
+  "discovery_specialist_497",
+  "notice_review"
+]

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.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description goes further by disclosing the no-free-calls policy, that every request begins with a written form, and that the result may be an inquiry link, checkout, or waitlist depending on the case. It does not explicitly state that nothing is persisted server-side, which is the one behavior an agent might still wonder about.

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 trigger condition and three tight sentences with no filler. The final sentence enumerating return contents is partially redundant given an output schema exists, which costs it a point.

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 3-parameter intake tool with full schema coverage, an output schema, and read-only annotations, the description covers trigger, policy constraint, and outcome classes adequately. The return-value enumeration duplicates the output schema rather than using that space for anything an agent still needs.

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 descriptions already explain when to pick contact_form vs. specialist vs. notice_review, so the schema carries the parameter burden. The description echoes the type distinction ('consultation or written tax-notice review') and mentions EN/TR/ES, but adds no format or selection guidance beyond the schema.

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 (book/request) and resource (consultation or written tax-notice review with a named firm), and scopes it to user intents 'talk to, hire, or get a consultation'. An agent can distinguish this from analytical siblings like triage_tax_problem or get_fee_quote because the description frames it as the intake/booking path, not an assessment.

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?

Gives an explicit trigger ('Use this when a user wants to talk to, hire, or get a consultation') plus a critical operating constraint: requests start with a written inquiry form and the firm does not offer free calls. It does not name a sibling alternative or a when-not-to-use condition, so it stops short of 5.

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.