Skip to main content
Glama

ingest_expense_receipt

Upload ONE expense receipt to put on a claim: it is held from automatic booking; poll get_expense_receipt, then attach its item_id with attach_claim_receipt. file_base64 is the file's raw bytes, base64.

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>",
      "filename": "<filename>",
      "file_base64": "<file_base64>"
    },
    "name": "ingest_expense_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes
company_idYes
file_base64Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the critical side effect: the upload is held from automatic booking, so processing is asynchronous and requires polling before the item_id is usable. It stops short of stating idempotency, size/format limits, or permission requirements for company_id.

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 with zero waste: the action and scope come first, the async-hold caveat second, the downstream call third, and the parameter clarification last. Nothing is repeated from the schema.

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 a 3-parameter write tool with no annotations and no output schema, the description covers the action, the async behavior, and the follow-up chain, which is what an agent needs to call it correctly. The remaining gap is the meaning/role of company_id and any constraints on the uploaded file.

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 compensate; it does explain the non-obvious parameter by defining file_base64 as the file's raw bytes, base64-encoded. filename is self-evident, but company_id is left unexplained (which company the receipt is filed under), so compensation is partial.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Upload ONE expense receipt") plus the scope constraint (single file, intended for a claim) and names the sibling it feeds into, attach_claim_receipt. An agent can distinguish it from the attach_* siblings without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives an explicit three-step sequence: upload, poll get_expense_receipt, then attach its item_id via attach_claim_receipt. This is real routing guidance rather than implied usage, though it never says when NOT to use it (e.g., when the receipt belongs to a cash entry and attach_cash_entry_receipt is the right follow-up).

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