Skip to main content
Glama

Quote a TRON Energy rental payable with x402

create_x402_quote

Lock a TRON Energy rental price for 10 minutes and pay in USDC via x402 without an account or API key; creates a free quote for Energy delegated to the target wallet.

Instructions

Locks a TRON Energy rental price for 10 minutes, payable in USDC on Base (or Solana) through x402. No account or API key. Energy is delegated to target_address, which must be the wallet that will SEND the USDT. Creating a quote costs nothing.

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": {
      "target_address": "<target_address>"
    },
    "name": "create_x402_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
energy_amountNoEnergy to rent. 65,000 fits a USDT transfer to a wallet that already holds USDT; use 130,000 for a wallet with no USDT.
target_addressYesTRON wallet that will send the USDT and should receive the Energy.
duration_secondsNoRental length in seconds: 3600 (1 hour) or 86400 (1 day).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare a non-readOnly, non-idempotent, non-destructive, open-world operation; the description adds real context beyond that: a fixed 10-minute price lock, zero cost to quote, no authentication, supported payment chains, and that Energy is delegated to the target wallet. It does not say what happens on quote expiry or whether re-quoting is required, leaving one behavioral 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?

Four compact sentences, front-loaded with what the tool does and the lock window, then prerequisites, then the critical address constraint. Every sentence carries operational information with no filler.

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?

The tool has no output schema, yet the description never says what a quote returns (a payment URL, quote id, or payment instructions) or how it is consumed by the follow-up rental call. For a simple three-parameter tool the input side is well covered, but the return-side gap leaves the agent guessing after invocation.

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 100%, including the energy_amount sizing guidance and the duration_seconds enum, so the schema already carries the parameter semantics. The description only restates the target_address constraint in prose, adding emphasis rather than new meaning, which is the baseline case for full coverage.

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?

States a specific verb and resource ('Locks a TRON Energy rental price') plus the payment rail (x402, USDC on Base/Solana) and the 10-minute window. This is clearly a quote-creation tool, distinguishable from sibling getters like get_x402_rental or get_energy_prices without opening either 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?

Gives concrete prerequisites ('No account or API key', 'Creating a quote costs nothing') and a hard usage constraint: target_address must be the wallet that will SEND the USDT. It stops short of explicitly sequencing against siblings (e.g., 'call this before get_x402_rental') or naming when not to use it, so it is clear context but not full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.