Skip to main content
Glama

Binyan.im · בניינים

Delete ledger entry

delete_ledger_entry
Destructive

Delete a refund, manual charge or manual credit from an apartment ledger. 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>",
      "entryId": "<entryId>"
    },
    "name": "delete_ledger_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
entryIdYes
buildingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=false, so the agent knows this is an irreversible-scope mutation. The description adds one genuinely new behavioral fact — that the action is audit logged — which is real value beyond the annotations. It still omits permissions required, whether deletion cascades to related records (offsets, payments), and what happens on failure, so it is additive but not rich.

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 with zero filler, and the resource scope is front-loaded ahead of the audit-logging note. Nothing is repeated from the title or annotations.

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, non-idempotent mutation with no output schema and two undocumented parameters, the description covers purpose and one behavioral trait but leaves parameter meaning, permissions and cascade behavior unexplained. Annotations partially offset this by making the destructive nature explicit, which is why this lands at minimum-viable rather than inadequate.

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 0%, so both required parameters (buildingId and entryId) carry no documented meaning in the schema, and the description does not compensate at all — it never mentions either parameter. The agent must guess that entryId is the ledger entry identifier and that buildingId scopes the lookup, which is a significant gap for a destructive operation where a wrong ID is costly.

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 (delete) and resource (ledger entry) and narrows the scope to refunds, manual charges and manual credits on an apartment ledger, which an agent can match against a target record. It does not distinguish itself from sibling delete tools such as delete_cash_box_movement or delete_offset, so the agent must infer the boundary from the resource noun alone.

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?

The enumerated entry types imply a usage restriction (only these three kinds of entries are deletable), which is useful implied guidance. However, there is no explicit when-to-use versus when-to-use-an-alternative statement, no prerequisites, and no mention of how to handle entries that are not one of the three listed types.

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