Skip to main content
Glama
Sign In
BlurHook MCP

BlurHook MCP

Official
by BlurHook
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List Uniswap v4 hooks and their pools

list_hook_pools
Read-only

List hook pools ranked by swaps, including pool counts, tokens, and recorded codehash pins. Filter by hook address to inspect its pools or by token to find hooks and pools that trade it.

Instructions

Hooks in the server's pool list ranked by swaps, with pool counts, tokens and recorded codehash pins. Pass a hook to list its pools, or a token to filter.

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": "list_hook_pools"
  }
}

Input Schema

NameRequiredDescriptionDefault
hookNoHook contract address: list its pools.
limitNoMax rows (default 25).
tokenNoOnly hooks or pools that trade this token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description usefully adds that data comes from "the server's pool list" and that results are ranked by swaps and include pool counts and codehash pins. It does not address default result volume or the interaction of the two filter modes beyond what the schema already says.

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?

Two tight sentences with the return content front-loaded and usage trailing. Nothing is redundant, though the phrasing is telegraphic ("recorded codehash pins") and requires the reader to infer what a pin is.

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 carries the burden of describing return values, and it does so reasonably: ranking, pool counts, tokens, codehash pins. It doesn't state whether rows are hooks or pools when unfiltered, which is the main missing piece for a zero-required-parameter listing 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%, so the schema already documents all three parameters, and the baseline is 3. The description restates the hook and token semantics in mode terms ("list its pools" vs "filter"), which is mildly additive, but it says nothing about limit or combining filters.

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 resource (Uniswap v4 hooks and their pools) and the shape of the returned data: ranked by swaps, with pool counts, tokens and codehash pins. It's clear what the tool returns, though it doesn't explicitly contrast itself with nearby siblings like hook_passport or blurhook_deployment.

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?

"Pass a hook to list its pools, or a token to filter" gives usable invocation guidance for the two modes, which is more than most definitions offer. However, there is no guidance on when to choose this over hook_passport or blurhook_deployment, and no statement about what happens when both hook and token are supplied.

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