Skip to main content
Glama

get_expense_report

Generate expense reports filtered by date range, user, client, project, and category. Group results by dimension and filter by billing status.

Instructions

Generate comprehensive expense reports with filtering by date range, users, clients, projects, and categories. Supports grouping and billing status filtering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromYesStart date for report (YYYY-MM-DD) (required)
toYesEnd date for report (YYYY-MM-DD) (required)
user_idNoFilter by specific user ID
client_idNoFilter by specific client ID
project_idNoFilter by specific project ID
expense_category_idNoFilter by specific expense category ID
billableNoFilter by billable status
is_billedNoFilter by billed status
updated_sinceNoFilter by expenses updated since this timestamp
group_byNoGroup report results by specified dimension
Behavior2/5

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

No annotations are provided, and the description does not disclose whether the report is read-only, what permissions are needed, or if it has side effects. It only states 'generate', which is ambiguous.

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 concise sentences with no wasted words; front-loaded with purpose and then details. Perfectly proportioned for a tool with many parameters.

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 no output schema, the description could mention the expected return format or result limits. However, it covers all key features (filtering, grouping, billing status) and is fairly complete for a report tool.

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?

The schema covers all parameters with descriptions (100% coverage). The description adds context by summarizing filtering dimensions and grouping, enhancing meaning beyond 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 clearly states it generates expense reports with filtering and grouping, distinguishing it from sibling report tools like get_time_report and get_uninvoiced_report.

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 use for expense reporting but does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites or 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/ianaleck/harvest-mcp-server'

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