Skip to main content
Glama

Remove the purchase

remove_collection_lot
Destructive

Remove exactly the one purchase that was previewed and that the user explicitly agreed to delete.

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": {
      "intent_id": "<intent_id>"
    },
    "name": "remove_collection_lot"
  }
}

Input Schema

NameRequiredDescriptionDefault
intent_idYesintent_id from prepare_moneteka_action, after the user saw its preview and agreed.

Output Schema

NameRequiredDescriptionDefault
dataYes
as_ofYes
warningsYes
request_idYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the danger is signposted structurally. The description adds real value by constraining the blast radius to exactly one previewed item and requiring prior explicit user consent, but it says nothing about reversibility or failure behavior when the intent_id is stale or already consumed.

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?

One sentence, front-loaded with the action and the cardinality constraint, with no filler. Every clause ("exactly one", "previewed", "explicitly agreed") carries an operational guardrail.

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 one-parameter destructive confirmation tool with full schema coverage and an output schema, the definition covers the essentials: single target, prerequisite tool, and user consent. Only post-conditions such as idempotency or what happens to the intent after success are left to the output schema.

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 the single intent_id parameter is fully documented in the schema, including its origin in prepare_moneteka_action and the preview/agreement precondition. The description only restates that precondition rather than adding format, expiry, or validation semantics beyond the schema.

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 a specific resource ("the one purchase that was previewed"), and narrows scope to a single item, which separates it from bulk-edit siblings like update_collection_lot. It does not explicitly name a contrasting sibling, and "purchase" differs from the tool name's "collection_lot", a minor terminology wobble.

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?

Implies the required workflow by stating the removal must target the previewed item the user agreed to delete, and the schema pins that preview to prepare_moneteka_action. It gives no explicit when-not guidance (e.g., use update_collection_lot instead of removing), so the agent must infer the alternative path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources