Skip to main content
Glama
Sign In

Beyond Payday

by com.beyondpayday
OverviewDiscussionsAdmin

Delete a what-if scenario

beyondpayday_delete_scenario
Destructive

Deletes a saved what-if scenario (the household's real data is untouched). It can be restored for 30 days with beyondpayday_restore_deleted. Get the id from beyondpayday_list_scenarios. Pass the scenario's updated_at as expected_updated_at so a scenario changed since is not deleted. Only the family owner or spouse/partner can do this, with What-if planner update plus income, bills and assets access. Figures are estimates from user-entered data — not tax, financial, investment, insurance, or legal advice.

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": {
      "scenario_id": "<scenario_id>"
    },
    "name": "beyondpayday_delete_scenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
scenario_idYesThe scenario id (beyondpayday_list_scenarios).
expected_updated_atNoThe updated_at from your last read of this scenario. If it changed since, the call is refused so you can re-read instead of overwriting someone else's change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=false, and the description goes meaningfully beyond them: it discloses the soft-delete/30-day restore window, the optimistic-concurrency refusal behavior on stale updated_at, and the permission prerequisites. These are exactly the traits an agent needs before invoking a destructive tool.

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 operative guidance (delete scope, restore path, id source, concurrency, permissions) is front-loaded and dense. The trailing disclaimer about estimates/advice is boilerplate that doesn't advance the delete task, though it is short.

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

Completeness5/5

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

No output schema is present, but the description covers the recovery path, authorization, and concurrency semantics, leaving nothing an agent needs in order to call it correctly.

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?

Schema coverage is 100% and both properties are already documented, so the description only adds procedural value (where to source the id) and restates the concurrency rationale. Useful but largely duplicative of schema field descriptions.

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 ('Deletes a saved what-if scenario') and immediately scopes it by clarifying that household real data is untouched. This separates it from the other delete_* siblings at a glance without needing 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 the agent: use beyondpayday_list_scenarios for the id, beyondpayday_restore_deleted to undo within 30 days, and pass expected_updated_at to avoid clobbering concurrent changes. It also names who may call it (owner or spouse/partner with planner + income/bills/assets access).

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

All Beyond Payday toolsInspect
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