Skip to main content
Glama

Mark payment as paid

mark-payment-paid
DestructiveIdempotent

Marks an open payment (an instalment of an expense, e.g. a deposit) as paid today, or on the given date; the budget totals follow. On a payment that is already paid, it overwrites the paid date. Payment ids come from get-budget.

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": {
      "payment_id": "<payment_id>"
    },
    "name": "mark-payment-paid"
  }
}

Input Schema

NameRequiredDescriptionDefault
paid_onNoYYYY-MM-DD, default today.
payment_idYesFrom the open payments in get-budget.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses the concrete destructive effect — overwriting an existing paid date — and the downstream side effect that budget totals change. It does not say whether the overwrite is reversible or what the response contains, but the key mutation risks are surfaced.

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 dense sentence with the core action and overwrite semantics front-loaded, then the id provenance. The semicolon-chained 'the budget totals follow' is slightly terse but conveys a real side effect efficiently; nothing is padding.

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?

For a 2-parameter mutation with no output schema and safety already in annotations, the description covers the object, the default date, the overwrite behavior and the side effect. Minor remaining gap: no statement of reversibility or resulting state after the call.

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 100%, and the schema already documents 'YYYY-MM-DD, default today' and the id source. The description restates the date default ('today, or on the given date') without adding format or edge-case detail, so the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('marks an open payment ... as paid') and even defines the resource ('an instalment of an expense, e.g. a deposit'), so an agent knows exactly what object is affected. The 'open payment' scoping and the paid-date overwrite clause make the operation unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the prerequisite source of ids ('Payment ids come from get-budget') and clarifies the already-paid case, which is the main ambiguity an agent could hit. It stops short of explicit when-not-to-use guidance or pointing at an alternative for reverting a payment.

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