Skip to main content
Glama

Add Transaction

add_transaction

Record income or expense transactions to automatically update account balances. Provide a positive amount; the sign is applied based on the category type.

Instructions

Record an income or expense transaction. Automatically updates the account balance. Provide a positive amount — the sign is applied based on the category type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesTransaction date in YYYY-MM-DD format.
tagsNoTags for categorization and cleanup, e.g. ['demo-financial'].
amountYesTransaction amount (positive number — sign is derived from category type).
account_idYesUUID of the capital account to debit/credit.
category_idYesUUID of the category (income or expense).
customer_idNoUUID of the customer this transaction is attributed to (e.g. a client payment). Optional.
descriptionYesDescription of the transaction.
exclude_from_reportsNoSet true to exclude from P&L reports (e.g. owner draws). Default false.
Behavior3/5

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

Mentions automatic balance update, which is beyond annotations (none provided). However, lacks details on permissions, error conditions, or return behavior.

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?

Two sentences with no redundant information. Efficiently communicates core purpose and a key usage detail.

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

Completeness2/5

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

With 8 parameters, no output schema, and no annotations, the description is too minimal. Does not address behavior for tags, customer_id, exclude_from_reports, or success/error responses.

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?

Adds clarity beyond schema by explaining sign derivation from category type. Schema already covers 100% of parameters, but description adds meaningful context for amount usage.

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?

Clearly states 'Record an income or expense transaction' with specific verb and resource. Distinguishes from siblings like 'add_account' or 'transfer_between_accounts' by focusing on transaction recording.

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 guidance on providing positive amount and sign derived from category, but does not explicitly state when to use this tool vs alternatives or any exclusions.

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/OurThinkTank/founders-os'

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