Skip to main content
Glama

Babelii-Diofis Account

Perbarui harga pesanan yang disiapkan

renew_purchase
Idempotent

Requote an unexecuted intent without another order or debit. Supply its current quote_version (initially 1). Returns the same intent_id, a new quote_version and up to five more minutes, at most three renewals within thirty minutes. Show the latest price/details and ask for confirmation again; execute with the returned version. Retrying the same input returns the saved renewal. Expired paid inquiries are not repeated automatically.

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>",
      "quote_version": "<quote_version>"
    },
    "name": "renew_purchase"
  }
}

Input Schema

NameRequiredDescriptionDefault
intent_idYes
quote_versionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations it discloses the concrete renewal budget and window ("at most three renewals within thirty minutes"), the grace period gained ("up to five more minutes"), the no-charge property ("without another order or debit"), and that expired paid inquiries are not repeated. It also confirms the idempotent-retry behavior the annotation hints at, saying retries return the saved renewal.

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?

The definition is front-loaded with the core action and then layers constraints and workflow in short, information-dense clauses; almost every sentence carries operational detail. It is telegraphic rather than wasteful, though a slightly more explicit sequencing would read more cleanly.

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?

For a two-parameter renewal tool with an output schema, this covers everything an agent needs: preconditions, the version handshake, renewal limits, retry semantics, and the required user-confirmation step. Nothing essential is left to guesswork.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, and it does for the non-obvious one: "Supply its current quote_version (initially 1)." It conveys intent_id's role indirectly through "Returns the same intent_id" and "execute with the returned version," leaving only intent_id's format unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a specific verb and resource with scope: "Requote an unexecuted intent without another order or debit." It also draws the boundary against execute_purchase by stating that no order or debit occurs and that execution happens only after the returned version is supplied.

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 qualifying condition (unexecuted intent), the required follow-up workflow ("Show the latest price/details and ask for confirmation again; execute with the returned version"), and the limits (three renewals within thirty minutes). It stops short of saying what to do once renewals are exhausted or explicitly naming prepare_purchase/execute_purchase as alternatives.

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