wallos-mcp

Overview Schema Source Related Servers Discussions Admin

Delete a subscription

delete_subscription

DestructiveIdempotent

Permanently removes a subscription from Wallos. Confirm the ID first because deletion cannot be undone; set inactive: true instead to stop paying while keeping history.

Instructions

Permanently removes a subscription from Wallos. There is no undo, so confirm the id first with list_subscriptions. To stop paying for something but keep the history, prefer setting inactive: true instead.

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": "delete_subscription"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Id of the subscription to delete.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description reinforces the destructive nature ('no undo') and adds the real operational guidance – verify the id first via list_subscriptions. It does not add much beyond the annotation that wasn't already implied, but the confirmation step is genuine extra context.

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 short sentences, front-loaded with the irreversible consequence, then the prerequisite, then the alternative – each sentence earns its place with zero filler.

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?

For a single-parameter destructive deletion with no output schema, the description covers what an agent needs: irreversibility, the id-verification prerequisite, and the softer alternative. Nothing material is missing.

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 there is a single required integer id already described as 'Id of the subscription to delete.' The description adds only the procedural hint to confirm it first rather than anything about the parameter's semantics, so this is baseline territory.

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 (permanently removes) and resource (a subscription from Wallos), and immediately names the sibling tools that bound its scope (list_subscriptions, update_subscription). An agent can tell it apart from update_subscription or list_subscriptions without opening either 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?

Explicit when-to-use (confirm id first with list_subscriptions) and when-not / alternative (prefer inactive: true to keep history). Both the safe path and the substitute are named, leaving nothing to inference.

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