Skip to main content
Glama

Binyan.im · בניינים

Attach expense receipt

attach_expense_receipt
DestructiveIdempotent

Attach or replace the receipt or invoice file of an existing expense, and optionally set vendor and invoiceNumber. Send either fileBase64 with mimeType (PDF, JPEG or PNG, up to 3 MB) or an https url (up to 10 MB, public hosts only, no redirects). The file is stored like receipts uploaded in the app.

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>",
      "expenseId": "<expenseId>"
    },
    "name": "attach_expense_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
vendorNo
filenameNo
mimeTypeNo
expenseIdYes
buildingIdYes
fileBase64No
invoiceNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Goes well past the annotations: annotations only flag destructiveHint=true, while the description explains that the destructive part is replacing an existing receipt file. It adds hard operational constraints absent from structured data — 3 MB base64 vs 10 MB url, PDF/JPEG/PNG only, public hosts only, no redirects — and notes the file is stored like in-app uploads.

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?

Two sentences, front-loaded with purpose before the input-mode rules, and every clause carries information. The dense parenthetical of constraints is justified by what it conveys, though the closing sentence about in-app storage is slightly vague.

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

Completeness4/5

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

For an 8-parameter mutation with no output schema, the description covers the risky parts: upload modes, size/type limits, host restrictions, and that replacement destroys the prior file. It omits what the call returns and whether vendor/invoiceNumber are left untouched when not supplied, which an agent must still infer.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must carry the load, and it does for the important parts: the fileBase64+mimeType pairing, the alternative url path with its limits, and the optional vendor/invoiceNumber fields. It leaves filename unexplained (e.g. whether it overrides the stored name) and takes buildingId/expenseId for granted, so one parameter remains undocumented at both levels.

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 ('attach or replace the receipt or invoice file of an existing expense') plus the secondary effect of setting vendor and invoiceNumber, so the agent knows exactly what is created. It does not name a sibling such as update_expense to draw the boundary explicitly, 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 Guidelines3/5

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

Provides the precondition that the expense must already exist and gives an operative rule for choosing between fileBase64 and an https url with size caps per mode. It never says when to use this instead of update_expense or create_expense, nor what to do if a receipt already exists beyond 'replace', so usage is implied rather than spelled out.

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