Moby

Token overviews (many at once)

get_token_overviews

Read-only

Overviews for up to 50 Solana tokens in one call. Use for many tokens at once (watchlists, scan qualifiers, portfolio marks): one call replaces up to 50 get_token_overview calls. Results are in request order: found: true with overview (the get_token_overview body, compacted) or found: false with error; one bad token never fails the call. Costs 1 read per 10 tokens. data_notes lists fields Moby lacks or knows only in part; verify those on the web before quoting them.

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": {
      "token_addresses": "<token_addresses>"
    },
    "name": "get_token_overviews"
  }
}

Input Schema

Name	Required	Description	Default
`token_addresses`	Yes	1-50 Solana token mint addresses. Duplicates are collapsed.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 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/openWorld/non-destructive, and the description adds substantial behavior beyond them: results in request order, per-item `found`/`error` shape, partial-failure isolation ('one bad token never fails the call'), a cost model (1 read per 10 tokens), and a caveat that `data_notes` fields may be incomplete and need web verification. The cost and partial-failure semantics are exactly the kind of disclosure annotations cannot carry.

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?

Front-loads the capability and the batch-vs-single routing, then packs return shape, failure isolation, cost, and the data-quality caveat into one dense but waste-free paragraph. Every clause carries information an agent needs to call it correctly.

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?

For a single-parameter batch read with an output schema and full annotation coverage, the description covers routing, partial-failure semantics, cost, and data caveats. Nothing an agent needs in order to invoke it correctly is missing.

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?

Schema coverage is 100% and the single parameter is fully documented there, so baseline is 3. The description adds meaning beyond the schema by tying the 50-item cap to batching behavior and stating that result order mirrors request order, which matters for correlating the returned array.

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+resource+scope: 'Overviews for up to 50 Solana tokens in one call.' It also explicitly contrasts with the sibling, noting one call replaces up to 50 `get_token_overview` calls, so an agent can route between batch and single without opening either 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 concrete use contexts (watchlists, scan qualifiers, portfolio marks) and implies the batch-vs-single split via the `get_token_overview` comparison. It never states an explicit when-not or names the single-token tool as the alternative to pick, leaving that routing one small inference away.

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

All Moby 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?