Skip to main content
Glama

Search tokens

search_token
Read-only

Find Robinhood Chain tokens by ticker, name, or 0x contract address. Searches the Stock Token registry and Blockscout index together so you can locate a token and its details in one query.

Instructions

Find tokens on Robinhood Chain by ticker, name, or contract address — searches the Stock Token registry and the Blockscout index together.

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_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 20).
queryYesTicker, name fragment, or 0x address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior context by disclosing that results come from the Stock Token registry and the Blockscout index combined, but says nothing about result ordering, de-duplication, or what happens if one source fails or lags.

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?

A single sentence that front-loads the action and scope, then closes with the source composition. No filler, no redundancy.

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 two-parameter read-only search with full schema coverage and no output schema, the description covers what is searched and where the data comes from. The only meaningful gap is that it does not characterize the result set (fields returned, ordering, or whether registry and index hits are merged), which matters because no output schema exists.

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 description coverage is 100%, so both 'query' (ticker, name fragment, 0x address) and 'limit' (max 50, default 20) are already documented. The description only restates the accepted query forms, adding no syntax, matching-behavior, or ranking detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Find'), resource ('tokens'), chain ('Robinhood Chain'), and the three lookup keys (ticker, name, contract address), plus the two underlying data sources. That clearly separates it from a bulk enumerator like list_stock_tokens, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the lookup-key framing: it is the tool you reach for when you have an identifier and want to resolve it. There is no explicit when-to-use / when-not-to-use guidance and no named alternative for browsing or listing all tokens.

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