Skip to main content
Glama
Sign In
Stables MCP Server

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete document

delete_document
DestructiveIdempotent

Removes a document from a transfer or payment route deposit; this action is irreversible, so confirm with a human before proceeding.

Instructions

Remove a document from a transfer or a payment route deposit. This cannot be undone, so confirm with a human first.

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": {
      "on": "<on>",
      "transactionId": "<transactionId>",
      "documentId": "<documentId>"
    },
    "name": "delete_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYesWhat the document belongs to: a transfer, or a deposit on a payment route
documentIdYesThe document ID from list_documents
transactionIdYesThe transfer ID, or the deposit ID from get_virtual_account_history

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.6.11
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv2.4.0

TDQS

A4/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 adds valuable operational context beyond that: the deletion is irreversible and requires human confirmation before invoking.

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?

Two short sentences, both informative, with the irreversible nature and human-confirmation requirement front-loaded. Nothing is wasted.

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 destructive single-record delete with fully documented parameters and destructive/idempotency annotations, the description supplies the essential missing piece (human confirmation + irreversibility). It omits error/not-found behavior, but the core decision inputs are present.

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 description coverage is 100%, so the schema already explains all three parameters including the transfer/deposit enum. The description's phrase 'from a transfer or a payment route deposit' loosely maps to the `on` field but adds no syntax or format detail beyond the schema; baseline 3 applies.

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?

States a specific verb (remove) and resource (document) plus the supported scopes (transfer or payment route deposit). It is clearly distinguishable from add_document/list_documents, though it does not name a sibling explicitly.

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?

Gives a concrete usage prerequisite: confirm with a human first, which is a meaningful gate for a destructive operation. It does not describe when-not-to-use or name alternatives, so it stops short of the top score.

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

Deploy Server

Other Tools