Skip to main content
Glama
Sign In
BlurHook MCP

BlurHook MCP

Official
by BlurHook
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Token USD prices

token_price
Read-only

Fetches live USD prices for up to 30 Robinhood Chain tokens using Uniswap v3/v4 quotes, directly via USDG or through ETH, so agents can value tokens before swaps.

Instructions

USD price per whole token from live Uniswap v3/v4 quotes, directly against USDG or via ETH (USDG counts as 1 USD). Up to 30 tokens.

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": {
      "tokens": "<tokens>"
    },
    "name": "token_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokensYesToken addresses, or ETH.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/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, and the description usefully adds the price source (live Uniswap v3/v4 quotes), the quote route (USDG direct or via ETH), and the USDG=1 USD peg convention. It stops short of disclosing what happens when a token has no pool or the quote fails, which is the main behavioral unknown left.

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 dense sentence with the resource and unit front-loaded, followed by source, route, and batch cap. Every clause carries information an agent needs, and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of describing the return value; 'USD price per whole token' gives the unit but not the response shape (mapping keyed by address vs array) or ordering. It also omits failure semantics for unpriceable tokens on a one-parameter query tool, leaving real gaps for an agent to discover at call time.

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% and the single parameter already carries the address pattern and the 'on Robinhood Chain, or ETH' explanation. The description only reinforces the batch cap of 30 (duplicating maxItems) and adds the 'whole token' unit framing, which is more about the result than the input, so baseline 3 applies.

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 states a specific resource and unit — 'USD price per whole token' — plus the data source (live Uniswap v3/v4 quotes) and the routing method (directly against USDG or via ETH). It does not differentiate itself from the sibling 'quote' tool, which an agent could plausibly pick for the same pricing intent, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative such as 'quote' or 'stock_tokens'. The only scoping hint is the incidental 'Up to 30 tokens' limit; the agent must infer the rest from the purpose 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