Skip to main content
Glama

MERX - TRON Resource Exchange

by exchange.merx

get_order

Read-onlyIdempotent

Get order status by UUID. Aliases: get_order_status, check_order, order_status, order_details, fetch_order. Check the status and fill details of an existing order by its UUID. Returns current status (PENDING/FILLING/FILLED/PARTIAL/FAILED/CANCELLED), fill amounts, provider used, on-chain delegation tx hash if delivered. Use this to poll order progress after creating an order. Auth required (API key).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesThe order UUID.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds value by detailing the returned fields (status, fill amounts, provider, tx hash) and noting auth requirement (API key). No contradiction.

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?

Description is compact and front-loaded, with aliases and usage context included. A brief extra sentence on return values is warranted. No fluff; slightly crowded with aliases but efficient.

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 simple 1-parameter getter with no output schema, the description covers purpose, return values, usage context, and auth. Missing error/not-found behavior, but overall complete enough.

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% with order_id described as 'The order UUID.' The description reinforces this by mentioning 'by UUID' but adds little beyond the schema. Baseline 3 is appropriate.

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?

Clearly states the verb and resource: 'Get order status by UUID' and 'Check the status and fill details of an existing order by its UUID.' Differentiates from siblings like list_orders by focusing on a single order lookup, and provides aliases for discoverability.

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 'Use this to poll order progress after creating an order,' giving a clear when-to-use context. Does not enumerate exclusions or compare to alternatives, but the context is sufficient for a simple lookup tool.

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

All MERX - TRON Resource Exchange toolsInspect
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

B3.4/5.0
Disambiguation3/5

With 66 tools, there is notable overlap between pricing tools (get_prices, get_best_price, compare_providers, get_price_history), balance/account tools (get_balance, get_account_info, get_trx_balance, get_trc20_balance), and order tools (get_order, list_orders, get_standing_order, list_standing_orders). While descriptions differentiate them, the sheer number and aliases (e.g., estimate_transaction_cost with 5 aliases) create ambiguity and potential for misselection.

Naming Consistency4/5

Naming is mostly consistent using snake_case (e.g., create_order, approve_trc20). However, there is variation in verb placement: some start with verbs (create_order, get_balance) while others with nouns (agent_status, resource_broadcast). Patterns like wait_for_delegation break the simple verb_noun structure, but overall the style is uniform.

Tool Count2/5

66 tools is far beyond typical MCP server sizes (3-15). While the domain is complex, many tools are utilities (convert_address, validate_address, explain_concept) that could be combined or omitted. The high count suggests scope creep and may overwhelm agents.

Completeness3/5

The server covers core workflows (buy resources, transfer tokens, check balances, create monitors/standing orders) but has notable gaps: order cancellation is missing (no cancel_order), many entities lack update/delete (e.g., invoices, monitors have cancel but no update), and execute_intent is not fully wired. Still, the surface is reasonably complete for its stated purpose.

Resources