Skip to main content
Glama

Confirm a conversion

confirm_conversion

Starts a conversion that waits for a go-ahead because it costs more than its maxCredits. Spends the shown credits: ask the user first. Waits up to 100 seconds for the result.

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": {
      "id": "<id>"
    },
    "name": "confirm_conversion"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe conversion id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly=false, idempotent=false, openWorld=true), and the description adds genuinely non-obvious behavior: it consumes credits, requires human confirmation, and blocks for up to 100 seconds. It stops short of disclosing timeout or failure semantics, which matter for a non-idempotent credit-spending call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, all load-bearing, with the cost/confirmation warning placed before the blocking-wait detail. The first sentence is slightly convoluted ('starts a conversion that waits for a go-ahead') but never padded.

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 mutating tool with no output schema, the description covers the essentials: cost, consent requirement, and the ~100 second wait for a result. The remaining gap is behavior on timeout or failure, which an agent calling a non-idempotent paid endpoint would benefit from knowing.

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 a single parameter (id) at 100% schema description coverage, so the schema already carries the semantics. The description adds only contextual framing ('the shown credits'), which does not enrich the id parameter itself; 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?

The description states a concrete action: it launches a previously-priced conversion that requires a go-ahead, spends credits, and blocks for the result. It distinguishes itself implicitly from convert by framing this as the paid-confirmation path that exceeds maxCredits, though it never names a sibling to contrast with 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?

It gives a clear triggering condition (cost exceeds maxCredits, so a go-ahead is needed) and an explicit procedural rule: ask the user first. What it lacks is a named alternative for the non-costly case (e.g. convert) and any note on what to do if the user declines or credits are insufficient.

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.