Skip to main content
Glama

Ledger integrity check

submit_ledger_integrity_check
Idempotent

Check that every journal entry and the ledger as a whole balance, and flag malformed rows. After posting a journal, before closing the period. Do not choose this when account-code or period validation is required. Example requests: Check whether this ledger balances. | Find the unbalanced journal entries. | Audit this journal for double-sided rows.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_ledger_integrity_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare idempotent, non-destructive, non-open-world behavior, and the description adds that malformed rows are flagged alongside balance checks. However, it never discloses the priced-job authorization flow (quote_id/accepted_price) that is central to this submit_* family, nor what the output flags look like beyond the phrasing. Useful but not rich behavioral disclosure.

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?

Purpose first, then timing, then exclusion, then sample requests – front-loaded and each sentence carries distinct information. The example requests are compact and help retrieval without bloating the text.

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?

With an output schema present, return values need no explanation, and the check semantics, timing, and exclusions are covered. The one gap is the priced-capability authorization flow, which the description ignores even though it is required for invocation.

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 75% and the nested journal parameter is well documented as a max-1MB CSV with a header row, so the schema does most of the work. The description clarifies what is checked inside the journal (per-entry and whole-ledger balance) but adds nothing about the quote_id, authorized_by, or accepted_price parameters.

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?

States a specific verb and resource: 'Check that every journal entry and the ledger as a whole balance, and flag malformed rows' – an agent immediately knows it verifies journal/ledger balancing and detects malformed rows. The exclusion ('Do not choose this when account-code or period validation is required') further separates it from validation siblings, though it never names which sibling to use instead.

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 explicit timing guidance ('After posting a journal, before closing the period') and an explicit when-not ('Do not choose this when account-code or period validation is required'). It stops short of naming the alternative tool to pick for account-code/period validation, leaving that inference to the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources