Skip to main content
Glama

verify_rental_crypto_payment

Verify the exact rental prepayment on the named mainnet using its tx_hash. Execution starts only after sufficient confirmations. No wallet private key is requested; one transaction cannot pay multiple rentals or product orders.

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": {
      "rental_id": "<rental_id>",
      "tx_hash": "<tx_hash>"
    },
    "name": "verify_rental_crypto_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
tx_hashYes
rental_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose non-obvious traits: verification is confirmation-gated before execution proceeds, no private key is ever requested (a trust signal for callers), and one transaction cannot satisfy multiple rentals or product orders. It still omits what a failed or under-confirmed verification returns and whether repeated calls are idempotent.

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 short sentences, front-loaded with the action and the identifying input, then the behavioral constraints. Nothing is redundant, though the mainnet phrase adds a small amount of noise given it has no corresponding parameter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a verification tool with no annotations and no output schema, the description should at least indicate what a successful versus failed verification means and what the caller gets back. It covers the preconditions well but leaves the outcome semantics and return shape to inference.

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 description coverage is 0%, so the description must compensate, and it only partly does: tx_hash is identified as the transaction hash and the one-transaction-one-rental rule implies the rental_id/tx_hash pairing is exclusive. The 'named mainnet' phrasing is also slightly confusing since no mainnet parameter exists in the schema, and neither parameter's format is described.

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 uses a specific verb (verify) and a scoped resource (rental prepayment), plus the discriminator 'using its tx_hash'. That is enough to separate it from the generic verify_crypto_payment sibling, though it never names or contrasts that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: you call this after paying a rental, since 'execution starts only after sufficient confirmations' frames it as a post-payment gate. There is no explicit statement of when to choose this over verify_crypto_payment, nor any stated exclusion or prerequisite for obtaining the rental_id.

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