Skip to main content
Glama

Binyan.im · בניינים

Delete cash box movement

delete_cash_box_movement
Destructive

Delete an explicit cash box deposit or transfer. The action is audit logged.

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": {
      "buildingId": "<buildingId>",
      "movementId": "<movementId>"
    },
    "name": "delete_cash_box_movement"
  }
}

Input Schema

NameRequiredDescriptionDefault
buildingIdYes
movementIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered structurally. The description adds one genuinely useful behavioral fact — the action is audit logged — but says nothing about reversibility, permission requirements, or side effects on linked ledger entries.

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?

Two short sentences, zero filler, with the action and its scope front-loaded. Every sentence contributes distinct information (what is deleted, and the audit-logging consequence).

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 destructive two-parameter mutation with no output schema, the description covers what is deleted and that auditing occurs, but leaves the parameters entirely unexplained and omits failure modes or reversibility. It is adequate to recognize the tool but not fully adequate to invoke it confidently without inspecting the schema.

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?

With 0% schema description coverage, both required parameters (buildingId, movementId) are undocumented in the schema, and the description adds no meaning about their format, source, or relationship. The agent must guess where movementId values come from and why buildingId is required alongside it.

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 names a specific verb (Delete) and a specific resource (an explicit cash box deposit or transfer), narrowing scope beyond a generic deletion. The qualifier 'explicit' hints at which movements qualify, though it never names the sibling tools (delete_ledger_entry, delete_offset) it differs from.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives such as delete_ledger_entry or delete_offset. The only implicit signal is the 'explicit cash box deposit or transfer' scoping, which an agent must interpret on its own.

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