Arc & Ledger Tax Tools

List fixed-fee products

list_products

Read-only

Use this when a user wants to know what Arc & Ledger sells at a fixed published price, or wants to buy one of those products (for example an EIN application, an S corporation election, an ITIN application, a tax extension, registered agent service, or an IRS notice review). Returns each product with its published price, billing interval, what it covers, and a first-party checkout link. Filter by category, by words, or by product id. Read-only: it does not take payment or place an order.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_products"
  }
}

Input Schema

Name	Required	Description
`query`	No	Words to match against product names and descriptions, for example "EIN" or "S corp" (optional). Every word must match.
`category`	No	Limit the list to one catalog category (optional).
`product_id`	No	Return exactly one product by its catalog id, for example "ein-application" (optional).

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.

Changed1 schema field changedNov 12, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "Business Formation",
-  "Compliance",
-  "IRS Help",
-  "International",
-  "Bundle",
-  "Diagnostics"
-]New value: +[
+  "Business Formation",
+  "Compliance",
+  "IRS Help",
+  "International",
+  "Bundle",
+  "Diagnostics",
+  "Tax Returns",
+  "Bookkeeping"
+]

AddedNov 11, 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, destructiveHint=false, and openWorldHint=true; the description adds that it 'does not take payment or place an order,' reinforcing the safety boundary in user-facing terms. It also previews the return shape (price, billing interval, coverage, checkout link), though it says nothing about pagination or result limits.

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-loads the trigger condition, then the return contents, then the read-only caveat — a logical order with no filler. The parenthetical product examples are long but earn their place by giving the agent vocabulary for matching user intent.

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 zero-required-parameter read-only lister with a full output schema and read-only annotations, the description covers trigger, scope, filters, return contents, and safety. The only remaining gap is routing to quote-style siblings when a user needs custom pricing, which is left implicit.

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 coverage is 100%, so all three filters are already documented in detail, including the 'every word must match' matching rule and the category enum. The description's 'filter by category, by words, or by product id' restates the schema without adding semantics such as how filters combine or which takes precedence.

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 and resource with clear scope: 'what Arc & Ledger sells at a fixed published price.' The phrase 'fixed published price' implicitly separates it from quote-oriented siblings such as get_fee_quote and get_itemized_quote, so an agent can distinguish it without opening another 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?

Gives a concrete trigger: 'when a user wants to know what Arc & Ledger sells at a fixed published price, or wants to buy one of those products.' The pricing qualifier effectively excludes custom-quote situations, but no alternative tool is named and no explicit when-not guidance is offered.

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.