Skip to main content
Glama

Cash Drawer Closeout

bpj_cash_drawer_closeout
Read-onlyIdempotent

Reconcile the starting float, cash receipts, refunds and drops with the final counted drawer balance.

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": {
      "opening": "<opening>",
      "receipts": "<receipts>",
      "cashRefunds": "<cashRefunds>",
      "drops": "<drops>",
      "count": "<count>"
    },
    "name": "bpj_cash_drawer_closeout"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYes
dropsYes
openingYes
receiptsYes
cashRefundsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds no behavior beyond that: it doesn't say what the tool returns (a variance amount, a balanced/not-balanced flag, an expected-drawer figure) despite there being no output schema, nor does it state sign conventions or how a discrepancy is reported.

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?

A single well-formed sentence with no padding, front-loading the verb and resource. It could be marginally stronger by ordering the inputs to match the schema or by appending the return-value expectation, but nothing is wasted.

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

Completeness3/5

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

For a five-required-parameter pure calculator with no output schema, an agent knows what to pass but not what comes back or how the reconciliation is computed. Minimum viable for invocation, but incomplete for interpreting the result of a reconciliation — the one thing the tool exists to produce.

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 description coverage is 0% — parameters carry only bare titles. The description does map natural-language concepts onto every required parameter (starting float→opening, cash receipts→receipts, refunds→cashRefunds, drops→drops, final counted balance→count), which is genuine added value. However it never states the arithmetic convention (are refunds and drops subtracted from the expected drawer?), currency, or rounding behavior, so a caller must guess the semantics that matter most.

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 ('Reconcile') and a specific resource/operation (cash drawer closeout) and enumerates the components being reconciled (float, receipts, refunds, drops, counted balance). An agent can tell this is a drawer reconciliation computation, though it doesn't distinguish itself from cash-related siblings like bpj_cash_runway or bpj_excess_cash_sweep beyond the domain nouns.

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?

Use at end-of-shift/end-of-day closeout is only implied by 'final counted drawer balance'; there is no explicit when-to-use, when-not-to-use, or alternatives guidance. Nothing tells an agent what to do if the drawer doesn't balance or which sibling handles other cash checks.

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.