Skip to main content
Glama
ArmandSwirc

TimeChimp MCP Server

by ArmandSwirc

get_expenses

Retrieve and filter expense data from TimeChimp with options for pagination, date ranges, and specific criteria like user, project, or customer.

Instructions

Retrieve all expenses from TimeChimp

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNoMaximum number of expenses to return (1-10000, default: 100)
skipNoNumber of expenses to skip for pagination (default: 0)
countNoWhether to include the total count of results (default: true)
expandNoComma-delimited list of properties to expand (e.g., "user,project,customer")
user_idNoFilter by specific user ID
project_idNoFilter by specific project ID
customer_idNoFilter by specific customer ID
from_dateNoStart date for filtering (YYYY-MM-DD format)
to_dateNoEnd date for filtering (YYYY-MM-DD format)
filterNoOData filter expression (e.g., "amount gt 100" or "approved eq true")
orderbyNoOData orderby expression (e.g., "date desc" or "amount desc")
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal information. It states 'Retrieve all expenses' but doesn't mention pagination behavior (implied by skip/top parameters), authentication requirements, rate limits, error conditions, or what format the expenses are returned in. For a tool with 11 parameters and no annotations, this leaves significant behavioral gaps.

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 extremely concise at just 5 words, front-loading the core purpose with zero wasted words. Every word earns its place, making it easy for an agent to quickly understand the basic function before examining the detailed schema.

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?

For a tool with 11 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain the filtering capabilities, pagination approach, or return format. While the schema covers parameter details, the description fails to provide the contextual understanding needed to effectively use this tool, especially given the complexity implied by the many filtering options.

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 description provides no parameter information, but the schema has 100% description coverage with detailed documentation for all 11 parameters including defaults, formats, and examples. Since schema_description_coverage is high (>80%), the baseline score of 3 is appropriate - the schema does the heavy lifting, and the description adds no additional parameter semantics.

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 verb ('Retrieve') and resource ('all expenses from TimeChimp'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its sibling 'get_expense_by_id' which retrieves a specific expense, nor does it mention the filtering capabilities that distinguish it from a simple list-all operation.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention that this is for listing expenses with optional filtering versus 'get_expense_by_id' for retrieving a single expense, nor does it provide context about when filtering parameters should be used. The agent receives no usage direction beyond the basic purpose.

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/ArmandSwirc/TimeChimpMCP'

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