Skip to main content
Glama

attach_cash_entry_receipt

Attach a receipt to a posted cash-book entry: a new file (file_base64, the raw bytes, base64) OR an existing document's item_id, exactly one. override_duplicate only after a duplicate refusal you checked.

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": {
      "company_id": "<company_id>",
      "register_id": "<register_id>",
      "entry_id": "<entry_id>"
    },
    "name": "attach_cash_entry_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idNo
entry_idYes
filenameNoreceipt.pdf
company_idYes
file_base64No
register_idYes
override_duplicateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations are absent, so the description carries the full burden. It does disclose two important behavioral traits: that only one of file_base64/item_id may be supplied, and that override_duplicate is a recovery path after a duplicate refusal rather than an upfront option. It omits permissions required, whether an existing attachment is replaced or an error is raised, size/type limits, and what the duplicate check keys on.

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 sentences with no filler, and the file-or-item choice plus the duplicate caveat are front-loaded in that order of importance. Loses a point only for the inline RST double-backtick markup, which is noise in an agent-facing string.

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 seven-parameter mutation with no annotations and no output schema, the description covers the genuinely ambiguous inputs but says nothing about what comes back, whether an attachment can be removed or replaced, or what a duplicate refusal looks like. An agent could invoke it, but not fully predict the outcome.

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 description coverage is 0%, so the description must compensate. It adds real meaning for file_base64 ('the raw bytes, base64'), the item_id alternative and the override_duplicate guard, but leaves filename, entry_id, register_id and company_id entirely to name inference.

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 states a specific verb and resource: 'Attach a receipt to a posted cash-book entry', and immediately enumerates the two acceptable receipt sources. The target resource ('posted cash-book entry') reasonably separates it from attach_claim_receipt, though it never says so explicitly.

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 gives one genuine conditional rule — call only after a checked duplicate refusal before using override_duplicate — which is real when-to-use guidance. Beyond that, there is no guidance on choosing this over attach_claim_receipt or ingest_expense_receipt, and no statement of prerequisites such as the entry needing to already be posted.

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