IQ Books by ReconcileIQ

Get one record

get_document

Read-onlyIdempotent

The full detail of ONE record whose id you already have (from find, a report or another tool). Choose its kind: a sales invoice or credit note, a bill, a journal, a bank transaction, a purchase order, an expense claim, a customer, supplier, account, bank account, stock item, fixed asset or project. Returns every field plus its lines where it has them (invoice, bill, journal and order lines), what each VAT code on it means, and for a supplier their CIS set-up (rate, UTR, verification). Read-only: it changes nothing and costs no credits. To search or list records use find; for the paper in the Documents inbox use list_documents, and read_document to have RiQ read one.

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": {
      "kind": "<kind>",
      "id": "<id>"
    },
    "name": "get_document"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The record id, as find or another tool returned it.
`kind`	Yes	The type of record: the same kind you would pass to find.
`organisation_id`	No	Which books. Leave it out to use the books chosen with select_organisation, or the only set this account has.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 30, 2026

addedInput schema / properties / id / description

Added value: +"The record id, as find or another tool returned it."

addedInput schema / properties / kind / description

Added value: +"The type of record: the same kind you would pass to find."

addedInput schema / properties / organisation_id / description

Added value: +"Which books. Leave it out to use the books chosen with select_organisation, or the only set this account has."

First observedOct 30, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by saying it costs no credits, that it returns every field plus line items, VAT code meanings, and supplier CIS set-up (rate, UTR, verification). That is real behavioral and return-shape context the annotations do not provide.

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?

The key scope statement is front-loaded and every later sentence carries routing or return-value information. The long enumeration of record kinds is the one passage that could be trimmed against the schema enum.

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?

With no output schema, the description takes on the burden of explaining returns and does so (all fields, line items, VAT codes, CIS set-up). Combined with clear routing to siblings, an agent has everything needed to call it correctly.

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%, so the baseline is 3; the description earns extra credit by giving business meaning to the kind enum ('a sales invoice or credit note, a bill, a journal...') and by tying id back to 'find or another tool'. It does not mention organisation_id, and 'credit note' is not an enum value, so it falls short of 5.

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 ('The full detail of ONE record') and immediately narrows the precondition ('whose id you already have'). It is clearly separable from find, list_documents and read_document, which are all named.

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?

Explicitly routes the agent: use this when you already have an id and want full detail; use find to search or list; use list_documents for the Documents inbox; use read_document to have RiQ read one. Preconditions and alternatives are both stated.

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?