Skip to main content
Glama

My Budget Control

Check MBC expense approval

expense_status
Read-only

Read whether the user approved a prepared expense. Only state recorded means it was booked; pending is not success.

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": {
      "draftId": "<draftId>"
    },
    "name": "expense_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 safety is covered. The description adds genuinely useful state interpretation — 'recorded' means booked and 'pending' is not success — which prevents an agent from misreporting an unbooked expense. It stops short of enumerating the possible states or saying what happens for an unknown or missing draft.

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?

Two short sentences with no filler, and the core action is front-loaded before the state caveat. The phrasing 'Only state recorded means it was booked' is slightly compressed and reads awkwardly, but nothing is redundant.

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 one-parameter read tool with no output schema, the description covers the essential state interpretation but leaves the return surface unclear — whether the result is a status string, boolean, or object with other values. It is adequate for safe invocation but not complete enough to fully interpret the response.

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% for the single required parameter draftId; only the JSON Schema supplies uuid format and a pattern. The description gestures at 'a prepared expense' but never states that draftId is the identifier of that prepared expense draft, nor where to obtain it, so an agent gains almost no meaning beyond the type constraint.

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 opens with a specific verb and resource: 'Read whether the user approved a prepared expense.' That tells an agent this is a read of an approval state for an already-created expense draft, which distinguishes it from prepare_expense (a write) and get_budget (a different resource). It is clear but never explicitly contrasts itself with those siblings.

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?

Usage is only implied: an agent can infer you call this after preparing an expense to confirm booking, and the second sentence warns that 'pending is not success.' There is no explicit statement of when to call it versus siblings, no prerequisites, and no note on whether it should be polled or called once.

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