Skip to main content
Glama
chiKeka

Alberta Tax Agent

by chiKeka

Record Receipt from Photo

record_receipt

Record a transaction from a receipt photo, linking the image as proof for expense tracking. Provide vendor, date, total, and optional details.

Instructions

Record a transaction from a receipt photo (PNG, JPG, JPEG). Claude reads the image, you provide the extracted details, and I'll create the transaction with the image linked as proof. This is how you digitize paper receipts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesReceipt date (YYYY-MM-DD)
notesNoAdditional notes about this receipt
totalYesTotal amount on the receipt ($)
vendorYesVendor/store name (from the receipt)
categoryNoExpense category override (e.g., 'office_supplies', 'meals_entertainment')
subtotalNoSubtotal before tax ($) — if visible on receipt
gst_amountNoGST amount ($) — if shown separately on receipt
image_pathYesPath to the receipt image (PNG, JPG, JPEG)
is_revenueNoIs this a revenue receipt (payment received)?
line_itemsNoIndividual items on the receipt (if you want to itemize)
descriptionNoWhat was purchased (brief description)
Behavior4/5

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

With no annotations, the description carries full burden. It discloses the workflow (Claude reads the image, user provides details, transaction created with proof), which is valuable behavioral context. It does not mention side effects or error cases, but the core mutation and proof-linking behavior are clear.

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?

The description is two sentences, front-loaded with the essential action, and includes a key use case in the last sentence. No wasted words, highly scannable.

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?

Given 11 parameters, 4 required, and no output schema, the description provides enough context for the core workflow. It clarifies the role of the image and proof, but leaves detailed param nuances to the schema. The tool is well-scoped and the description is sufficient for an agent to understand its role.

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?

The schema has 100% parameter description coverage, so the baseline is 3. The tool description itself does not add parameter-level details beyond the schema, but it does mention 'you provide the extracted details' as a workflow hint. This is sufficient but not exceptional.

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?

The description states a specific action ('Record a transaction from a receipt photo'), identifies the resource (receipt photo), and clarifies the output (transaction with image linked as proof). It distinguishes itself from sibling tools like record_transaction and scan_receipts_folder by focusing on photo digitization.

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?

The description implies when to use the tool ('This is how you digitize paper receipts') and contrasts with broader record tools. It clearly covers the single-receipt photo scenario but does not explicitly state alternatives or exclusions (e.g., when to use record_transaction instead).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chiKeka/alberta-tax-agent'

If you have feedback or need assistance with the MCP directory API, please join our Discord server