Skip to main content
Glama

Change the purchase

update_collection_lot
Destructive

Apply the previewed and approved correction to exactly one existing purchase.

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": "update_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

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: this is not an ad-hoc edit but the application of a previously previewed and user-approved intent, and it affects exactly one purchase. It does not discuss reversibility or what an expired/consumed intent_id does, leaving a minor gap.

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?

A single short sentence with the precondition and the scope front-loaded and no filler. Every clause earns its place.

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?

With one fully documented parameter and an output schema present, return values need not be described, and the description covers the essential precondition and mutation scope. It could go slightly further on edge cases (stale or already-applied intents) for a destructive mutation, but the definition is otherwise sufficient to call it correctly.

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?

There is only one parameter and schema coverage is 100%, so the schema already explains that intent_id comes from prepare_moneteka_action after the user agreed to the preview. The description adds only the scoping phrase 'exactly one existing purchase' and does not elaborate on identifier format or lifetime rules 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?

The description states a concrete verb and scope: 'Apply the previewed and approved correction to exactly one existing purchase,' which tells an agent precisely what happens and to how many records. The only weakness is terminology drift between the tool name/title ('collection_lot', 'purchase') and the description, but the intent is still unambiguous when read alongside 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 Guidelines4/5

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

Usage is clearly gated: the correction must have been previewed and approved first, and the schema ties intent_id back to prepare_moneteka_action. This gives an agent a clear precondition for calling it. It stops short of naming exclusions (e.g., when to use add_collection_lot/remove_collection_lot instead), so no explicit when-not guidance is present.

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