Skip to main content
Glama
Sign In

Switchbooks

by ai.switchbooks
OverviewDiscussionsAdmin

Review Reconciliations

manage_reconciliations
Read-onlyIdempotent

Review reconciliation history or compare an account with a statement ending date and balance. A preview identifies differences before a reconciliation is finished. Set action to one of: history, preview.

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

Input Schema

NameRequiredDescriptionDefault
dateNo
fileNo
namesNo
actionNo
amountNo
offsetNo
accountNo
companyNoCompany for this call only: its ID, exact name, or a unique part of the name. Leave out to use the active company.
excludeNo
skipBeforeNo
statementsNo
openingBalanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this as a safe, read-only, idempotent, non-destructive operation. The description adds a useful behavioral detail—that preview identifies differences before a reconciliation is finished—but it does not describe return format, pagination, or other traits beyond what annotations provide.

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

Conciseness5/5

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

The description is three sentences, front-loaded with the core purpose, then adds the preview behavior, and ends with the action instruction. Every sentence contributes and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 12 parameters, no output schema, and only 8% schema description coverage, the description is far too sparse to guide correct invocation. It omits parameter semantics, does not distinguish the two actions beyond naming them, and provides no return-value context for a tool of this complexity.

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

Parameters2/5

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

Schema description coverage is only 8%, so the description must compensate for 12 mostly undocumented parameters. It mentions the 'action' enum values, but that is already in the schema, and it does not explain what 'date', 'file', 'names', 'amount', 'offset', 'account', 'exclude', 'skipBefore', 'statements', or 'openingBalance' mean or how they interact.

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 states a specific verb and resource: 'Review reconciliation history or compare an account with a statement ending date and balance.' It is clear what the tool does, but it does not differentiate itself from any sibling tool or clarify that it is not for creating or editing reconciliations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies usage by describing two modes: reviewing history and comparing with a statement. 'A preview identifies differences before a reconciliation is finished' gives some when-to-use context for the preview action, but there are no explicit alternatives or exclusions and no guidance on when to choose history versus preview beyond the action values.

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

All Switchbooks toolsInspect
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