Ringske

Update expense

update-expense

DestructiveIdempotent

Changes an expense: name, amount, category, linked vendor or notes. Only the fields you pass change. A per-guest expense takes per_guest_amount instead of amount. Payment instalments are managed in the dashboard; mark one as paid with mark-payment-paid.

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": "update-expense"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The expense, from get-budget.
`name`	No
`notes`	No
`amount`	No	Fixed amount in euro, e.g. "1500".
`category`	No	Budget category name; created when new. Empty string for none.
`vendor_id`	No	Link to a vendor from list-vendors; null to unlink.
`purchased_on`	No	YYYY-MM-DD.
`per_guest_amount`	No	Price per guest in euro, only for per-guest expenses.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=true; the description adds the important PATCH-style clarification that unpassed fields are preserved, which materially tempers the destructive read. It does not mention permissions or what happens when an unknown category or vendor_id is supplied, so a small gap remains beyond the annotations.

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?

Three sentences, front-loaded with the mutation and its fields, then the partial-update rule, then the sibling routing. No filler and no restatement of the title.

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 an 8-parameter mutation with no output schema, it covers the mutation semantics, the mutually exclusive amount fields, and the instalment alternative, which is enough to call it safely. Missing only edge-case behavior for invalid category or vendor references.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Goes beyond the 75%-covered schema by declaring the amount versus per_guest_amount exclusivity rule for per-guest expenses, which the schema only hints at via a per-parameter description. Other parameters (name, note formatting, purchased_on) get no added meaning, so it is not exhaustive.

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 plus resource ('Changes an expense') and enumerates the mutable fields, which cleanly separates it from add-expense, delete-expense and mark-payment-paid in the sibling list. An agent can identify the tool without opening the schema.

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

Usage Guidelines5/5

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

Explicitly routes work away from this tool: instalments are managed in the dashboard and marking one paid belongs to mark-payment-paid. It also states that partial updates are expected ('Only the fields you pass change'), which is the key usage condition for an update call.

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

All Ringske tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?