Skip to main content
Glama

create_expense

Record a new expense in Moxie by providing amount, date, and description, with options to allocate to a client or vendor, set reimbursement, and add notes.

Instructions

Create a new expense record in Moxie

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesExpense date in ISO-8601 format (e.g., 2023-07-20T00:00:00.000+00:00)
paidNoWhether the expense has been paid or is due in the future
notesNoAdditional notes about the expense
amountYesExpense amount
billNoNoBill/reference number
vendorNoExact match of a Vendor record name in Moxie
categoryNoExpense category
currencyNoISO 4217 currency code (e.g., USD, EUR). Defaults to workspace currency
clientNameNoExact match of a client record name to allocate this expense to
descriptionYesDescription of the expense
reimbursableNoWhether the expense is eligible for reimbursement through invoicing
markupPercentageNoMarkup percentage for reimbursable expenses when applied to invoice
Behavior2/5

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

No annotations provided, so the description must disclose behavioral traits. It only states the creation action without mentioning side effects, permissions, or constraints (e.g., duplicate handling, billing implications).

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?

Single sentence, clear and concise. No unnecessary words, though more detail could be added without harming conciseness.

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?

Despite 12 parameters and no output schema, the description provides minimal context. No information about return value, error handling, or operational effects, leaving the agent underinformed.

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 coverage is 100%, so the baseline is 3. The description does not add additional meaning beyond the parameter descriptions in the schema.

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 'Create a new expense record in Moxie' clearly identifies the action (create) and resource (expense record). It distinguishes from sibling tools as no other tool targets expenses.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, prerequisites, or exclusions. The description only states the basic function.

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/SabryParra/moxie-mcp'

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