Skip to main content
Glama

Get expense

get_expense
Read-only

Get one expense, including whether a receipt is attached.

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

Input Schema

NameRequiredDescriptionDefault
expense_idYes
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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 one genuine behavioral fact beyond that: the response includes receipt-attachment status, which is useful for deciding whether a follow-up like add_expense_receipt is needed. It does not describe the rest of the returned record, though no output schema exists to cover that gap.

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 receipt detail is placed after the core purpose. It is efficient, though the brevity contributes to the guidance and parameter gaps noted elsewhere.

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?

For a low-complexity single-record read with full annotation coverage, the definition is minimally viable. However, with no output schema and an undocumented required parameter, an agent gets only a fragment of what the call returns and nothing about how to source expense_id.

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 only 50%: business_id is documented but expense_id has no description in the schema, and the tool description says nothing about either parameter. The description does not compensate for the undocumented required id, leaving an agent to infer its origin and format from the uuid type alone.

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 uses a specific verb ("Get") with a precise cardinality ("one expense"), which distinguishes it from the collection-style sibling list_expenses without needing to name it. It falls short of 5 only because it does not explicitly contrast itself with any sibling.

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 statement of when to reach for this tool versus list_expenses or get_finance_summary, and no prerequisite such as obtaining an expense_id from list_expenses first. Usage must be inferred entirely from the name and the word "one".

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