Skip to main content
Glama

create_expense

Create a project expense entry with category, cost, date, and optional billable status and receipt attachment.

Instructions

Create a new expense entry for a project with category and cost details. Supports receipt attachment and billable status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idNoThe user ID who incurred the expense
project_idYesThe project ID to associate the expense with (required)
expense_category_idYesThe expense category ID (required)
spent_dateYesDate the expense was incurred (YYYY-MM-DD) (required)
notesNoNotes or description for the expense
total_costYesTotal cost of the expense (required)
unitsNoNumber of units for unit-based expenses
billableNoWhether the expense is billable to the client
Behavior2/5

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

With no annotations, the description must disclose all behavioral traits. It fails to mention whether permissions are needed, side effects, or what happens on duplicate entries. It also misleadingly states 'supports receipt attachment' when no such parameter exists, reducing transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is fairly concise, but it includes a misleading claim about receipt attachment. It front-loads the core action but sacrifices accuracy for brevity, resulting in moderate conciseness.

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?

Given the complex input schema (8 parameters, 4 required) and no output schema/annotations, the description provides minimal context beyond the schema itself. It doesn't explain the return value, error handling, or constraints like uniqueness, leaving gaps for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides detailed descriptions for all 8 parameters (100% coverage). The tool description adds no new semantic value beyond mentioning 'receipt attachment' (not in schema) and 'billable status' (already described). This introduces confusion rather than clarity.

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?

The description clearly states the tool creates an expense entry for a project with category and cost details, distinguishing it from sibling tools like create_time_entry or create_invoice. However, it claims support for receipt attachment, which is not reflected in the input schema, causing slight ambiguity.

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?

The description implies when to use (creating an expense entry) but provides no explicit guidance on when not to use or alternatives among siblings like update_expense or list_expenses. The context is clear but lacks exclusions or comparative notes.

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/ianaleck/harvest-mcp-server'

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