Skip to main content
Glama

List expenses

list_expenses
Read-onlyIdempotent

The expenses of a range of days that this token sees (the same view as time entries), read only, with the spent amount and currency. Filter by project_id or member_id. from and to are ISO dates (YYYY-MM-DD) in the time zone of the workspace, both required, at most 366 days, both dates included. Pages: page from 1 and per_page up to 100; next_page is null on the last page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "list_expenses"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesThe last day: the range is at most 366 days, both dates included
fromYesThe first day
pageNoFrom 1
per_pageNo50 by default
member_idNoOnly this member
project_idNoOnly this project

Output Schema

NameRequiredDescriptionDefault
dataYes
pageYes
per_pageYes
next_pageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description adds real value on top: token-scoped visibility ('the same view as time entries'), a 366-day cap, inclusive endpoints, workspace-timezone interpretation, and the pagination terminal condition (`next_page` is null). It stops short of noting rate limits or error behavior.

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?

One dense paragraph, front-loaded with scope and return fields, then filters, then date rules, then pagination — a logical order with no filler sentences. The backtick-heavy phrasing and stacked clauses make it slightly harder to scan than it needs to be.

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

Completeness5/5

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

With an output schema present, return values need not be re-explained, and the description still covers the constraints an agent must respect: required inclusive date range, maximum span, filter options, and page termination via next_page. Nothing needed to call it correctly is missing.

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 and the schema already documents each parameter. The description does add meaning beyond it: ISO date format and workspace timezone, both dates included, the 366-day ceiling, page starting at 1, per_page up to 100, and next_page semantics for termination.

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?

Names the resource (expenses), the scope (a range of days, the same view as time entries) and the payload fields (spent amount and currency), which lets an agent distinguish it from get_expense and list_time_entries. It lacks an explicit verb and never contrasts itself with the singular get_expense sibling by name, keeping it short of a 5.

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?

Implies usage through 'read only' and the filter options ('Filter by project_id or member_id'), and the required from/to make the call shape obvious. It never states when to prefer this over get_expense or how it relates to time entries beyond visibility, so guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources