Skip to main content
Glama

Get an expense

get_expense
Read-onlyIdempotent

One expense by id, read only.

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": {
      "id": "<id>"
    },
    "name": "get_expense"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the expense

Output Schema

NameRequiredDescriptionDefault
idYes
noteNo
stateYes
amountYes
markupNo
receiptNo
billableNo
currencyYes
spent_onYes
client_idYes
member_idYes
invoice_idNo
project_idYes
updated_atNo
category_idNo
client_nameNo
inserted_atNo
member_nameNo
project_nameNo
billed_amountNo
category_nameNo
invoice_numberNo
billed_elsewhere_onNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so 'read only' merely restates structured data. Nothing is added about behavior when the id is unknown (error vs empty) or about the expense's shape beyond what the output schema carries.

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?

The definition is a single short clause with the scope front-loaded and zero filler. It is efficient, though the terseness borders on under-specification rather than polished concision.

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

Completeness3/5

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

With one required parameter, full schema coverage, and an output schema that describes the return value, the tool is simple enough that the terse description is barely sufficient. Missing pieces, such as the not-found behavior, keep it at minimum viable rather than complete.

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 description coverage is 100% and the single `id` parameter is documented as a UUID in the schema, so the description's 'by `id`' adds no new meaning. The baseline of 3 applies when the schema fully carries 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 names a specific resource and scope: a single expense retrieved by its `id`, which implicitly contrasts with the list_expenses sibling. It is clear but minimally worded, with the verb 'get' only implied by the name rather than stated.

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?

There is no guidance on when to use this tool versus list_expenses or any other sibling, and no stated prerequisites such as needing a known id. The agent must infer the usage context from the tool name alone.

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