Skip to main content
Glama

delete_purchase

Destructive

Remove a purchase logged by mistake from SmartCard after user confirmation to correct purchase history and reward tracking.

Instructions

Delete a purchase logged by mistake. Ask the user 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": {
      "purchase_id": "<purchase_id>"
    },
    "name": "delete_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
purchase_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description's added value is the confirmation requirement. However, it never states whether deletion is permanent, whether it can be undone, or what happens if the purchase_id is unknown, which are the facts a destructive tool most owes the agent.

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, front-loaded with the action and immediately followed by the required safeguard. No filler and nothing restated from schema or annotations.

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?

An output schema exists, so return values need not be described, and the annotations carry the destructive profile. For a single-parameter delete, the definition covers intent and the confirmation requirement without leaving critical call-time information out.

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?

Only one parameter, and the schema describes it at 0% coverage; the description does not explain that purchase_id is an integer identifier or where it comes from (e.g., list_purchases). With a single self-evidently named parameter the gap is modest, but it does not compensate for the missing schema documentation.

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?

The description gives a specific verb and resource ('Delete a purchase') plus a qualifier that narrows intent ('logged by mistake'), which separates it from the sibling log_purchase. It stops short of naming any alternative tool, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

'Ask the user first' supplies one concrete prerequisite (confirmation before invoking), which is real usage guidance for a destructive call. It says nothing about when deletion is preferable to correcting the record via a sibling such as update_card or adjust_rewards, and lists no exclusions.

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