Skip to main content
Glama

AwesomeFee: TRON energy, sending and node for AI agents

AwesomeFee: find TRON products for agents (energy, sending, node, events)

search
Read-onlyIdempotent

AwesomeFee — TRON resources for AI agents. Free. Finds what you need on TRON — e.g. "send USDT without TRX", "buy energy", "TRON RPC node", "events webhook" (English or Russian) — and returns catalogue entries: id, title, description, method, url, parameters (JSON Schema of the body), price, payment (free | x402 | pass), a curl example and what comes back. No q = the whole catalogue. Then call the returned URL yourself with an x402 v2 HTTP client (@x402/fetch, @x402/axios, Python x402): the first call answers 402 with the terms, your client pays in USDC on Base from YOUR wallet and repeats, you get the result. This server never pays and never holds keys.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoWhat you need, in words, e.g. "send USDT", "купить энергию", "rpc". Omit for the whole catalogue.
limitNo1–50, default 10 with q.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only mark it read-only/open-world/idempotent; the description adds what those annotations cannot — that results carry a price field (free | x402 | pass), that the paid path happens outside this server, that this server never pays and never holds keys, and that queries work in English or Russian. That is precisely the behavioural context an agent needs before committing to the downstream payment flow.

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?

Front-loaded with identity and purpose, then the return shape, then the payment flow; almost every clause carries information. The opening 'Free.' is slightly at odds with the later price/payment discussion and the sentence is dense, but nothing is truly wasted.

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?

With no output schema, the description does the work of enumerating the returned fields and even notes what comes back from the eventual URL call. The payment economics, wallet custody boundary, and zero-parameter default are all covered, leaving little an agent could get wrong at call time.

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 schema already documents both q and limit, including the omit-for-all-catalogue rule. The description restates 'No q = the whole catalogue' and adds bilingual query examples, but contributes no new syntactic or formatting meaning beyond the schema.

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 concrete verb and resource — 'Finds what you need on TRON' — plus the exact return shape (catalogue entries with id, title, method, url, price, curl example). Example queries ('send USDT without TRX', 'buy energy', 'TRON RPC node') pin the domain down far more sharply than the name 'search' would on its own.

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?

Explicitly says what happens with no q ('the whole catalogue') and then spells out the follow-up workflow: call the returned URL yourself with an x402 v2 HTTP client, expect a 402, pay in USDC on Base, repeat. There are no sibling tools to exclude, but there is no statement of when NOT to use it (e.g. what query types yield nothing) either.

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