Skip to main content
Glama

Add the purchase

add_collection_lot

Save the new purchase that prepare_moneteka_action previewed and the user approved.

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": "add_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 this is a non-read-only, non-destructive, closed-world write. The description adds the important two-phase constraint, that it depends on a prior preview plus user consent, which goes beyond the annotations. It says nothing about idempotency, whether intent_id expires, or what happens if the same intent is submitted twice.

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 sentence with no filler, front-loaded with the action and immediately qualified by the precondition. Nothing redundant or repeated from the schema.

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 commit tool with an output schema and annotations covering the safety profile, the definition covers the essentials. Only minor behavioral details (error/failure semantics, confirmation of what is added) are absent.

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 parameter is already documented in the schema, including its provenance. The description reinforces but does not extend that meaning, which is the baseline case for a fully documented one-parameter 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 gives a specific verb ("Save") and resource ("the new purchase"), and ties it to the sibling that generates the payload: prepare_moneteka_action. It is distinguishable from the prepare/update/remove siblings as the commit step, though it never uses the "collection lot" terminology from the tool name, leaving a small gap between name and description.

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?

It states the precondition explicitly: the purchase must have been previewed by prepare_moneteka_action and approved by the user. That amounts to clear when-to-use guidance. It stops short of naming exclusions, e.g. that update_collection_lot or remove_collection_lot should be used for subsequent changes.

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