Skip to main content
Glama

Attach receipt to expense

crunch_add_expense_attachment

Attach receipt or invoice files to an existing expense while preserving current attachments. Add supporting documents to an expense record without replacing files already uploaded.

Instructions

Attach one or more files (receipts, invoices) to an existing expense. Existing attachments are kept.

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": {
      "expense_id": "<expense_id>",
      "attachments": "<attachments>"
    },
    "name": "crunch_add_expense_attachment"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoPreview: return the request that would be sent (for an update, the fields that would change) without sending it
expense_idYesExpense ID (see crunch_list_expenses)
attachmentsYesFiles to attach

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so safety is largely covered. The description adds one genuinely valuable fact beyond that: 'Existing attachments are kept', clarifying the call is additive rather than replacing. It still omits what repeated calls do (duplicates, given idempotentHint=false) and what the response contains.

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 short sentences, front-loaded with the action and target, with zero filler. The brevity is appropriate for a simple append operation, though it leaves gaps that extra detail could have filled.

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 simple additive tool with no output schema and full schema coverage, the description covers the essentials: action, target, and additive semantics. It stops short of stating expected results (attachment IDs returned) or behavior on duplicate file names, which would matter given idempotentHint=false.

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 100%, including detailed descriptions of file_path vs content_base64 and dry_run, so the schema does the heavy lifting. The description only adds 'one or more files', which restates the array nature already in the schema rather than clarifying sourcing options.

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 ('Attach') and resource ('files (receipts, invoices) to an existing expense'), making the target entity clear. The expense-vs-invoice distinction is conveyed only implicitly through the word 'expense', so the sibling crunch_add_invoice_attachment is never explicitly ruled out, though the resource scope is unambiguous enough to route correctly.

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?

'to an existing expense' implies the prerequisite that the expense must already exist, and the schema points to crunch_list_expenses for the ID. However, there is no explicit when-to-use versus alternatives (e.g., when to attach to an invoice instead), no guidance on dry_run previewing, and no stated size/count limits.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools