Skip to main content
Glama
Sign In

TronSave

by io.github.tronsave
OverviewDiscussionsAdmin

Resource Price Table

tronsave_get_price_table
Read-onlyIdempotent

Read the price grid for ENERGY or BANDWIDTH: prices[i][j] is the unit price in SUN for amounts[i] resource units rented for durations[j] (e.g. '15m', '1h', '1d'). Durations of 1 day or longer are priced per day: '30d' at 40 SUN costs 40 x 30 SUN per unit in total. Use to compare cost across amounts and durations in one call. For an exact quote on one purchase use tronsave_estimate_buy_resource; for only the floor price use tronsave_get_min_price. Public, read-only.

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": {
      "resourceType": "<resourceType>"
    },
    "name": "tronsave_get_price_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressNoOptional receiver address; prices can depend on the account.
resourceTypeYesENERGY (smart-contract calls) or BANDWIDTH (plain transfers).

Output Schema

NameRequiredDescriptionDefault
pricesNo
amountsNo
durationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / resourceType / description
      Added value: +"ENERGY (smart-contract calls) or BANDWIDTH (plain transfers)."
  2. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, and the trailing 'Public, read-only' largely restates them. The genuinely additive content is the pricing semantics — SUN as the unit and the per-day rule for durations of 1 day or longer — which is behavior an agent cannot infer from annotations. Safety/auth surface is fully covered by annotations, so this lands mid-range.

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 the core definition and matrix indexing, then the per-day pricing caveat with a worked example, then routing guidance. Dense but every clause carries information; only the redundant 'Public, read-only' tail is arguably wasted given the annotations.

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 2-param read tool with a full output schema, the description covers the one thing the schema cannot: how to interpret the returned price grid and how per-day durations are charged. The per-day example ('40 x 30 SUN per unit in total') is slightly ambiguous about whether the multiple applies twice, but overall nothing essential is missing.

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 itself documents both the enum meaning and the address caveat ('prices can depend on the account'). The description adds no parameter-level detail for resourceType or address; its extra detail concerns the response matrix rather than the inputs, so the baseline of 3 applies.

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 ('Read the price grid for ENERGY or BANDWIDTH') and immediately defines the shape of what comes back (prices[i][j] keyed by amounts[i] and durations[j]). An agent can distinguish it from any other pricing sibling without opening the schema.

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

Usage Guidelines5/5

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

Explicitly says 'Use to compare cost across amounts and durations in one call', then names two alternatives with the condition that selects each: exact quote goes to tronsave_estimate_buy_resource, floor price only goes to tronsave_get_min_price. Clear when-to-use and when-not-to-use.

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

All TronSave toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources