Skip to main content
Glama

Arc hook risk

arc_hook_risk

What a Uniswap v4 hook on Arc is allowed to do, read from the permission bits in its address with no chain call: whether it runs on swaps or can rewrite amounts. A capability, not a verdict. $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "hook": "<hook>"
    },
    "name": "arc_hook_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
hookYes0x hook address from the pool key
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it reveals the method (local bit decoding, no RPC call), the cost ($0.003 per call), accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and the two-phase x402 handshake. It does not say how an invalid or EOA-style hook address is handled, which is the main remaining behavioral gap.

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?

Three tight sentences, front-loaded with the core capability before price and payment mechanics. 'A capability, not a verdict' is a high-value qualifier that prevents misreading the output, and no sentence is filler.

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?

Covers method, price, payment rails and the two-call protocol, and gestures at the returned capability flags despite there being no output schema. Adequate for a two-parameter paid lookup; only edge-case behaviour (invalid addresses, failed payment) is left unstated.

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 both `hook` (0x hook address from the pool key) and `payment` (base64 x402 payload) are already documented in the schema. The description adds the sequencing of `payment` (first call returns terms), but that is procedural rather than deepening either parameter's meaning, so the 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?

States a specific verb+resource: decodes the permission bits of a Uniswap v4 hook address on Arc to report what it may do (run on swaps, rewrite amounts). The scope 'with no chain call' and 'a capability, not a verdict' sharpen the boundary. It does not name a sibling (e.g. arc_contract_check, arc_trust_check) as the alternative, so differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

Gives an explicit operational procedure: call once without `payment` to obtain terms, sign them with your own wallet, call again with `payment` to complete the purchase. That resolves the main when/how question for a paid tool. It offers no guidance on when to choose this over the neighbouring inspection tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources