IQ Books by ReconcileIQ

Where these books are

books_status

Read-onlyIdempotent

Where a set of books has actually got to: how far the ledger runs, whether opening balances were ever set, bank accounts, what is waiting in Review, the VAT and MTD position, the stock valuation method and whether it has locked, and what is outstanding on the setup. Read this before answering "are these books up to date", before starting on a new client, and before any piece of work whose right answer depends on how much is already in. Give organisation_id to check books other than the selected ones. It answers area by area (how far the bank is written up and how many days behind, opening balances, bank accounts and feeds, what waits in Review, open documents, payroll, CIS, fixed assets, stock, VAT), each saying what is in and what is missing. For the figures use get_report; for what is due and when, use deadlines. It reads the ledger and changes nothing.

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": "books_status"
  }
}

Input Schema

Name	Required	Description	Default
`organisation_id`	No	Defaults to the selected organisation.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The description discloses that it reads the ledger and changes nothing, and describes the shape of the response (area by area, saying what is present and what is missing). This adds real context beyond the readOnly/idempotent/non-destructive annotations, though the 'changes nothing' line partly restates them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and usage triggers, but the coverage list is effectively given twice (the opening sentence and the 'answers area by area' clause), adding length without new information. The prose is dense and could be trimmed without losing meaning.

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?

No output schema exists, so the description must convey what comes back, and it does: a per-area breakdown covering bank write-up and days behind, opening balances, feeds, Review items, payroll, CIS, fixed assets, stock and VAT. Nothing essential for calling it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is self-documenting, so baseline applies. The description still adds value by explaining that supplying organisation_id checks books other than the currently selected ones, clarifying the practical reason to use it rather than merely restating 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 resource (the state of a set of books) and enumerates the areas it reports on, so an agent knows exactly what it returns. It explicitly contrasts itself with get_report (figures) and deadlines (what is due), so siblings are distinguishable without opening schemas.

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?

Gives concrete triggers: before answering 'are these books up to date', before starting a new client, and before any work whose answer depends on how much is already recorded. It also names the alternatives and the condition that selects each (get_report for figures, deadlines for due dates).

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

All IQ Books by ReconcileIQ 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.

Resources

Need Help?