Skip to main content
Glama

Look up expense reports

expense_lookup
Read-onlyIdempotent

Search expense reports by employee, status, category, date range, and amount, then view totals and policy notes such as approval thresholds and on-call meal limits.

Instructions

Search expense reports by employee, status, category, date range and amount, with totals and policy notes (approval thresholds, on-call meal limit). Read-only. Requires role: agent.

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": "expense_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
limitNoMax items per page (default 20, max 50)
cursorNoOpaque cursor from a previous page (next_cursor)
statusNo
categoryNo
min_amountNo
employee_idNoEmployee id, e.g. E004

Output Schema

NameRequiredDescriptionDefault
totalYes
expensesYes
by_statusNo
next_cursorYesPass as cursor to get the next page; null when done
total_amount_usdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 destructiveHint=false, so safety is covered. The description adds real value beyond them by disclosing the authorization requirement ('Requires role: agent') and the returned content (totals and policy notes such as approval thresholds and the on-call meal limit). It stops short of mentioning rate limits or pagination behavior.

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 tight sentences with zero filler. The filter list is front-loaded, then the return content, then the read-only and role constraints in the order an agent needs them.

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?

An output schema exists, so the description doesn't need to detail return values, though it helpfully flags totals and policy notes. Read-only status and the role prerequisite are both covered. The remaining gap is pagination/result-volume behavior for a list-style tool, which is only implied by the schema.

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 only 38% across 8 parameters, so the description must compensate, and it partially does by naming employee, status, category, date range, and amount filters. It doesn't clarify the enum values, the min_amount vs. amount distinction, or the from/to date semantics. Pagination params (limit, cursor) are left entirely to the schema descriptions.

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 names a specific verb ('Search') and resource ('expense reports') and enumerates the filter dimensions: employee, status, category, date range, amount. It also states what comes back (totals, policy notes). It doesn't explicitly distance itself from siblings, but no sibling in the catalog covers expenses, so the ambiguity risk is low.

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 one hard usage rule is stated: 'Requires role: agent'. It also implicitly frames the tool as a read-only lookup for policy/reimbursement questions. However, there is no explicit when-to-use or when-not guidance and no pointer to an alternative for creating or approving expenses.

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