TronSave MCP Server

Official

by tronsave

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

List Orders

tronsave_list_orders

Read-onlyIdempotent

Query and paginate TronSave market orders by status, resource type, or your wallet to find active or completed energy and bandwidth listings before trading.

Instructions

Query the market order list with paging (offset, limit ≤ 10). Returns { orders: [{ id, requester?.address, receiver.address, resourceType, resourceAmount, remainAmount, durationSec, unitPrice (SUN), isOwner, isMatching, apy, createdAt, typeOrder (NORMAL|FAST|EXTEND) }] }. status: ACTIVE = still matching, COMPLETED = no longer matching. Set isOnlyMyOrder=true (requires a wallet signature identity) to list orders requested by the caller's wallet. Use tronsave_get_order with an id for one snapshot before mutating an order.

Input Schema

Name	Required	Description
`limit`	No	Maximum rows to return in one call. Prefer modest limits to avoid huge payloads; page with `offset`.
`offset`	No	Zero-based row offset for page N (skip first `offset` matches). Omit when starting from the first page.
`status`	No	Lifecycle filter: `ACTIVE` = still matching/open, `COMPLETED` = no longer matching. Omit for both.
`resourceType`	No	Restrict to `ENERGY` or `BANDWIDTH` orders; omit for both.
`isOnlyMyOrder`	No	When `true`, only orders requested by the wallet of the current signature identity (signature login or `Signature` header). Api-key-only sessions cannot use this filter.

Output Schema

Name	Required	Description	Default
`orders`	No	Matching orders for this page; may be large—use pagination inputs to chunk.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.4.0Nov 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the description earns credit for adding an auth prerequisite (api-key-only sessions cannot use isOnlyMyOrder) and for spelling out what ACTIVE vs COMPLETED mean in matching terms. It does not cover result ordering, rate limits, or pagination ceiling behavior (offset max 200 is only in the schema).

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 action and paging cap, then filters, then the alternative. Slightly wasteful in that the full return shape is enumerated even though an output schema exists, and the status enum meanings duplicate the schema text.

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?

A read-only, zero-required-parameter list tool with annotations and an output schema needs exactly this: filter semantics, the auth caveat on one filter, paging bounds, and a pointer to the single-record sibling. Nothing an agent needs to call it correctly 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%, so the schema already documents all five parameters including enum meanings and the signature-identity caveat. The description largely restates those definitions and adds only the unit annotation for the output field unitPrice (SUN), so baseline 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 ("Query the market order list") plus the paging constraint, and explicitly routes single-record reads to tronsave_get_order with an `id`. An agent can distinguish it from the order-book and single-order siblings without opening a 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 clear usage context: paging via offset/limit, status filter semantics, and the prerequisite that isOnlyMyOrder requires a wallet signature identity. It names one alternative (tronsave_get_order for a single snapshot) but offers no guidance versus tronsave_list_order_books or the internal order-book siblings.

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

Deploy Server