Skip to main content
Glama
Sign In
BlurHook MCP

BlurHook MCP

Official
by BlurHook
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Quote a swap

quote
Read-only

Finds a swap route on Robinhood Chain across Uniswap v3, v4, and hooked pools, returning amounts, price impact, slippage checks, warnings, and a policy-verdict preview without calldata.

Instructions

Best route for a swap on Robinhood Chain across Uniswap v3 (4 fee tiers), v4 and hooked v4 pools, including splits and two-hop routes via USDG or ETH. Returns amounts, minimum received, price impact, pinned-code and hook checks, warnings, and a preview of the spending-policy verdict. Never returns calldata.

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": {
      "tokenIn": "<tokenIn>",
      "tokenOut": "<tokenOut>",
      "amount": "<amount>"
    },
    "name": "quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesAmount of tokenIn as a decimal string in whole-token units, e.g. "0.25".
tokenInYesToken address on Robinhood Chain, or "ETH" for native ETH.
tokenOutYesToken address on Robinhood Chain, or "ETH" for native ETH.
slippageBpsNoSlippage in basis points. Defaults to the policy maximum; above it the trade is refused.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's job is to add context, which it does: it enumerates the returned fields (amounts, minimum received, price impact, pinned-code and hook checks, warnings, spending-policy preview) and explicitly disclaims calldata output. It does not mention quote staleness or any rate/latency considerations, which would be the remaining useful detail.

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?

Two sentences and zero filler, with the routing scope front-loaded and the negative constraint ('never returns calldata') placed last for emphasis. Every clause carries operational information.

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 output schema, the description usefully enumerates what the quote returns and what it does not, and the fully-described schema covers inputs. It stops short of saying whether a quote must be refreshed before building the swap, which matters for a four-parameter pricing tool.

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%, including the slippageBps default and refusal-above-maximum behavior, so the schema already carries parameter meaning. The description adds no syntax or format detail beyond it, which matches the baseline 3.

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 action (quoting the best route for a swap) on a specific venue (Robinhood Chain, Uniswap v3/v4/hooked v4) with the routing scope spelled out (fee tiers, splits, two-hop via USDG or ETH). This lets an agent separate it cleanly from siblings like build_swap and simulate without opening any schema.

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?

The line 'Never returns calldata' implicitly routes execution to build_swap, but neither that tool nor simulate is named, and there is no explicit statement of when to prefer this over simulate or when a fresh quote is required. Usage is inferable rather than stated.

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