TronOrb — TRON analytics

Search TronOrb

search_tronorb

Read-onlyIdempotent

Search TronOrb for TRON dApps, tokens, exchanges, wallets, services and guides by name. Returns up to 12 matching pages with kind, name, a short detail and a key number (TVL or market cap). Use it when the user names a specific project, token or topic; to rank a whole section use list_projects. An empty results array means nothing on TronOrb matches — try a shorter or different name.

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": {
      "query": "<query>"
    },
    "name": "search_tronorb"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Name or keyword, e.g. "SunSwap", "USDD", "energy rental"

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds return-shape and result-cap behavior ('up to 12 matching pages', fields returned) and the empty-array semantics, which go beyond the annotations. It does not mention rate limits or ranking order, so not quite a 5.

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?

Three tight sentences: what it searches, what it returns, then when to use it vs. the sibling, plus a recovery hint. Front-loaded and no sentence is filler.

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?

There is no output schema, so the description compensates by naming the returned fields (kind, name, detail, key number such as TVL or market cap) and the 12-item cap. Combined with the routing guidance and empty-result explanation, an agent has everything needed to call and interpret it.

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?

Only one parameter and schema coverage is 100%, so the schema already documents the query format and gives examples. The description clarifies that queries can be project names, token names or topic keywords, which mildly extends the schema but does not add syntax or matching rules. 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 (search) and resource (TronOrb), enumerates the searchable entity kinds (dApps, tokens, exchanges, wallets, services, guides), and explicitly contrasts with list_projects. An agent can pick it over its siblings 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?

Gives an explicit trigger ('when the user names a specific project, token or topic') and names the alternative for the opposite case ('to rank a whole section use list_projects'). Also states what an empty result means and how to recover, which is real usage guidance.

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

All TronOrb — TRON analytics tools Inspect

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

Need Help?