Skip to main content
Glama

Binyan.im · בניינים

Record expense

create_expense

Record a building expense (הוצאה). A second call records another expense.

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>",
      "amount": "<amount>",
      "description": "<description>",
      "date": "<date>",
      "category": "<category>"
    },
    "name": "create_expense"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
amountYes
vendorNo
categoryYes
buildingIdYes
descriptionYes
cashBoxAmountNoPart of the expense paid from the building cash box.
invoiceNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / cashBoxAmount
      Added value: +{
      +  "description": "Part of the expense paid from the building cash box.",
      +  "minimum": 0,
      +  "type": "number"
      +}
  2. First observed

TDQS

C2.7/5.0
Behavior3/5

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

The line 'A second call records another expense' usefully reinforces that each invocation creates a separate record, consistent with idempotentHint=false, which is real added context beyond the annotations. However, it says nothing about validation rules, whether buildingId must already exist, currency handling, or whether a receipt/invoice is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the resource, which is good, but the second sentence ('A second call records another expense') is oddly phrased and largely restates what idempotentHint=false already declares, so it does not fully earn its place.

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

Completeness2/5

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

This is a creation tool with 8 parameters, low schema coverage, and no output schema; the description gives no indication of what a successful call returns or what a created record contains. For that complexity, two short sentences leave substantial gaps an agent would need in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 8 parameters, 5 required, and only 13% schema description coverage, the description must compensate and does not: it never mentions amount, category, date format, vendor, invoiceNumber, or how cashBoxAmount relates to amount. An agent gets zero semantic help for the majority of undocumented fields.

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: 'Record a building expense', with a Hebrew gloss (הוצאה) that disambiguates the domain term. It does not distinguish itself from siblings such as update_expense, attach_expense_receipt, or list_expenses, so it stops short of a 5.

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 guidance at all: nothing says when to create a new expense versus updating one, attaching a receipt, or recording a payment/refund. The reader must infer the calling context entirely from the tool name.

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