Skip to main content
Glama

Binyan.im · בניינים

Delete offset

delete_offset
Destructive

Delete an offset payment and its credit. The linked expense stays. 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>",
      "paymentId": "<paymentId>"
    },
    "name": "delete_offset"
  }
}

Input Schema

NameRequiredDescriptionDefault
paymentIdYes
buildingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and idempotentHint=false, so irreversibility is partly covered. The description does add genuinely new behavioral facts: the associated credit is also removed, the linked expense is preserved, and the action is audit logged. It stops short of stating permission requirements or whether the deletion can be undone.

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?

Three short, front-loaded sentences with no filler; the scope of deletion is stated before the side effects. Nothing is wasted, though the text could have spent those sentences on parameter meaning instead.

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 and no annotation-level detail, the description covers cascade scope and auditing but leaves parameter meaning and the response/confirmation behavior unexplained. Adequate but with clear gaps.

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% and both parameters are bare strings with only minLength constraints. The description never explains what paymentId identifies (the offset payment, presumably) or what role buildingId plays in scoping the deletion, so it does not compensate for the coverage gap.

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 ('Delete an offset payment') and disambiguates the cascade scope by saying the credit goes with it while 'the linked expense stays.' That is enough to tell it apart from record_offset or delete_ledger_entry, though it does not name a sibling alternative directly.

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 when-to-use or when-not-to-use guidance, no prerequisite stating that an offset must already exist, and no pointer to record_offset for creating one or to any reversal path. Usage is only implied by the verb.

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