Skip to main content
Glama

Binyan.im · בניינים

Record apartment charge

record_apartment_charge

Record a manual charge or a manual credit on one apartment. A charge behaves like an open charge: it consumes credit first, then appears as overdue or due soon by its date and is paid by normal payments. A manual credit is a positive correction.

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>",
      "apartmentId": "<apartmentId>",
      "amount": "<amount>",
      "description": "<description>"
    },
    "name": "record_apartment_charge"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDue date of the charge. Defaults to today.
typeNoMANUAL_CHARGE adds a debit, MANUAL_CREDIT adds a positive adjustment. Defaults to MANUAL_CHARGE.
amountYes
buildingIdYes
apartmentIdYes
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), and the description adds real domain behavior: credit is consumed first, the entry then surfaces as overdue or due soon by date, and normal payments settle it. It does not warn about duplicate creation despite idempotentHint=false, which is the main remaining gap.

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?

Three short sentences, front-loaded with the action and scope, then the charge mechanics, then the credit case. No filler and no repetition of the title.

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 six-parameter mutation with no output schema, the description covers the domain model well but omits what the call returns (e.g. the created ledger entry) and the meaning of the required identifiers and amount. Adequate to call safely, but not complete.

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 only 33%, so the description must compensate. It clarifies `type` semantics and how `date` drives overdue/due-soon status, but says nothing about `amount`, `buildingId`, `apartmentId`, or `description` (the four required fields), leaving half the parameter meaning to the schema.

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 and resource ('Record a manual charge or a manual credit on one apartment') and defines the two modes it supports. It is clear what the tool does, though it never names a sibling (e.g. record_payment or record_offset) to sharpen the boundary.

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?

It explains what a charge does (consumes credit first, becomes overdue/due soon, paid by normal payments) and that a credit is a positive correction, which helps pick the `type` value. However, it gives no explicit when-to-use-this-vs-another-tool guidance or exclusions, leaving tool selection to inference from sibling names.

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