Tronsave MCP Testnet

User Permissions

tronsave_get_user_permissions

Read-onlyIdempotent

Read the enabled permission operations (autoSettings.permitOperations) for the authenticated user. Returns { permitOperations: string[] } — use it before mutating auto-sell or auto-buy rules to confirm the action is allowed for the wallet. Requires a signature session and mcp-session-id. Read-only and idempotent.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`permitOperations`	Yes	Permission rows enabled for this user; defaults to `[]` when nothing is configured.

TDQS

A4.5/5.0

Behavior4/5

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

Annotations provide readOnlyHint, idempotentHint, and openWorldHint. The description adds beyond: authentication requirement ('signature session and mcp-session-id') and confirms read-only and idempotent nature. No contradictions.

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?

Two sentences: first states purpose and return, second gives usage guidance and prerequisites. No unnecessary words, well front-loaded.

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?

Given the tool is simple (no parameters, output schema exists), the description covers purpose, return format, usage context, and prerequisites. Complete for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are no parameters in the input schema (schema coverage 100%). The description adds value by specifying the return structure 'Returns { permitOperations: string[] }', clarifying what the tool outputs.

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?

The description clearly states 'Read the enabled permission operations...', with a specific verb and resource. It distinguishes from sibling tools by focusing on read-only permission checking, unlike mutation tools like tronsave_create_order.

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?

The description instructs to 'use it before mutating auto-sell or auto-buy rules to confirm the action is allowed', providing explicit context for when to use. It does not list alternatives but implicitly contrasts with mutation siblings.

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

All Tronsave MCP Testnet tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation2/5

Several tools have overlapping purposes, such as multiple order creation tools (tronsave_create_order, tronsave_internal_order_create, tronsave_internal_create_extend_request) and multiple estimation tools (tronsave_estimate_buy_resource, tronsave_get_min_price, tronsave_internal_order_estimate). This would confuse an agent trying to select the correct tool.

Naming Consistency3/5

Tools follow a tronsave_verb_noun pattern with snake_case, but verbs are inconsistent (e.g., list vs get, create vs register) and the internal_ prefix creates two distinct naming styles. Some tools like tronsave_internal_order_book and tronsave_list_order_books are confusingly similar.

Tool Count2/5

29 tools is excessive for a server focused on a single market. Many tools duplicate functionality for internal vs signature authentication, bloating the surface. A more streamlined set (e.g., 10-15) would be more appropriate.

Completeness3/5

The tool set covers core operations like CRUD for orders, account info, and auto-settings. However, there are gaps: no explicit delete for auto-sell settings, and manual sell is the only sell option. Some internal tools appear redundant, but overall coverage is adequate.

Resources

Need Help?