Skip to main content
Glama

Uitgaven

list_expenses
Read-only

Retrieve expense records for a chosen year or filter for entries missing receipts, with optional inclusion of voided expenses.

Instructions

List expenses, optionally for one year or only those still missing a receipt.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
yearNo
include_voidedNo
missing_receiptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds filter scoping but is silent on important behavior such as whether voided expenses appear by default, result ordering, or volume of returned records.

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?

A single front-loaded sentence with no filler; the core action leads and the filters follow. It is efficient, though the terse phrasing is what leaves include_voided unexplained.

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?

With no output schema and 0% schema coverage, the description is the only source of parameter meaning, and it omits include_voided entirely. For a simple list tool this is under-specified rather than complete.

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?

Schema description coverage is 0%, so the description must carry parameter meaning. It explains year ("for one year") and missing_receipt ("only those still missing a receipt") but never mentions include_voided, leaving one of three parameters entirely undocumented and the default voided-expense behavior unknown.

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 gives a specific verb and resource ("List expenses") and adds scope details about year and receipt status. It is unambiguous about what the tool returns, though it does not distinguish itself from siblings like list_invoices or the record/void expense tools.

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 word "optionally" signals that all filters are discretionary, but there is no guidance on when to reach for this tool versus record_expense, void_expense, or report tools. No prerequisites, no note on default behavior when no filters are given.

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