Skip to main content
Glama
Sign In
BlurHook MCP

BlurHook MCP

Official
by BlurHook
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Verified Robinhood Stock Tokens

stock_tokens
Read-only

Lists verified Robinhood Stock Tokens on Robinhood Chain by exact runtime-code match to the official proxy, and shows whether the spending policy permits trading each.

Instructions

Robinhood Stock Tokens on Robinhood Chain, listed only when the contract's runtime code exactly matches the official Stock Token proxy (copycats with the same symbol are never listed), with whether the spending policy allows trading each.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stock_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior beyond that: the runtime-code equality filter that excludes same-symbol copycats, and the per-token spending-policy allowance flag. It does not say how many tokens come back, ordering, or how the 'official proxy' is determined.

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?

A single front-loaded sentence with no filler; the anti-copycat clause is the most decision-relevant part and is placed early. The trailing 'with whether the spending policy allows trading each' is grammatically awkward but still earns its place by describing the returned flag.

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?

With no input params and no output schema, the description carries the burden of explaining what comes back, and it does so at a high level (verified tokens plus a tradability flag). Missing only secondary details like result size, ordering, or chain/network specifics.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline for a parameterless tool applies. The description correctly implies a no-argument full listing rather than a lookup.

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?

It names the concrete resource (Robinhood Stock Tokens on Robinhood Chain) and the key scope constraint (only contract-code-verified tokens; copycats with the same symbol excluded). The listing action is implied by 'listed' rather than stated as a leading verb, but an agent can still tell this apart from token_price or list_hook_pools.

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: the mention of 'whether the spending policy allows trading each' suggests this is a pre-trade discovery check before quote/build_swap/spending_policy calls. However, no sibling is named and there is no explicit when-to-use or when-not-to-use statement.

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

Deploy Server

Other Tools