Skip to main content
Glama
Sign In

NIGHTSHIFT public

by tech.getnightshift
OverviewDiscussionsAdmin

Hook Inspector ($0.05, explained $0.50)

hook_inspect
Read-onlyIdempotent

Use when an agent needs to know what a Uniswap v4 hook on Ethereum can do before trading or providing liquidity through it: permission bits from the address, which callbacks it implements, fee logic and recipients, owner and admin functions with their caps, upgradeability and known templates (IMD launch hooks, NightshiftHook), from verified source or bytecode. Run by NIGHTSHIFT. explain=true ($0.5) adds a written explanation with the source lines. Pass the x402 payment as payment.

Input Schema

NameRequiredDescriptionDefault
addressYesUniswap v4 hook address on Ethereum
explainNo
paymentNox402 payment: the base64 PAYMENT-SIGNATURE payload for this call's terms. Leave it out to get the terms.
holderWalletNoThe wallet that will pay, for the holder price (50% off). Holders pay half: a paying wallet that holds 500,000+ $SHIFT (in the wallet plus staked), a NIGHT FROG or a Night Watcher gets NIGHTSHIFT house checks and reports at 50%. Fast lookup holder prices have a $0.001 minimum. Swarm Desk orders cost the full quoted price. Ask with holder=<that wallet> (MCP: holderWallet) to get the holder terms, then pay from that wallet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / holderWallet / description
      Previous value: -"The wallet that will pay, for the holder price (50% off). Holders pay half: a paying wallet that holds 500,000+ $SHIFT (in the wallet plus staked), a NIGHT FROG or a Night Watcher gets NIGHTSHIFT house checks and reports at 50%. Swarm Desk orders cost the full quoted price. Ask with holder=<that wallet> (MCP: holderWallet) to get the holder terms, then pay from that wallet."New value: +"The wallet that will pay, for the holder price (50% off). Holders pay half: a paying wallet that holds 500,000+ $SHIFT (in the wallet plus staked), a NIGHT FROG or a Night Watcher gets NIGHTSHIFT house checks and reports at 50%. Fast lookup holder prices have a $0.001 minimum. Swarm Desk orders cost the full quoted price. Ask with holder=<that wallet> (MCP: holderWallet) to get the holder terms, then pay from that wallet."
  2. Changed1 schema field changed
    • changedInput schema / properties / holderWallet / description
      Previous value: -"The wallet that will pay, for the holder price (50% off). Holders pay half: a paying wallet that holds 500,000+ $SHIFT (in the wallet plus staked), a NIGHT FROG or a Night Watcher gets every NIGHTSHIFT house service at 50%. Ask with holder=<that wallet> (MCP: holderWallet) to get the holder terms, then pay from that wallet."New value: +"The wallet that will pay, for the holder price (50% off). Holders pay half: a paying wallet that holds 500,000+ $SHIFT (in the wallet plus staked), a NIGHT FROG or a Night Watcher gets NIGHTSHIFT house checks and reports at 50%. Swarm Desk orders cost the full quoted price. Ask with holder=<that wallet> (MCP: holderWallet) to get the holder terms, then pay from that wallet."
  3. Changed1 schema field changed
    • addedInput schema / properties / holderWallet
      Added value: +{
+  "description": "The wallet that will pay, for the holder price (50% off). Holders pay half: a paying wallet that holds 500,000+ $SHIFT (in the wallet plus staked), a NIGHT FROG or a Night Watcher gets every NIGHTSHIFT house service at 50%. Ask with holder=<that wallet> (MCP: holderWallet) to get the holder terms, then pay from that wallet.",
+  "pattern": "^0x[0-9a-fA-F]{40}$",
+  "type": "string"
+}
  4. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this a safe idempotent read, so the description does not need to re-litigate safety; instead it adds genuinely new behavior: data is derived from verified source or bytecode, NIGHTSHIFT is the operator, and the explain flag changes the response at a higher price. It stops short of saying what happens when a hook is unverified or unknown, which is the one failure mode an agent would want to know about.

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?

Everything is front-loaded: the when-to-use clause leads, capabilities follow, then operator and pricing. It is dense and slightly overstuffed with payment detail, but 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?

There is no output schema, so the description carries the return-shape burden, and it does so by listing the finding categories an agent will get back, plus the difference between the paid and free tiers. Missing are error/unknown-hook behavior and confirmation that scope is Ethereum-mainnet v4 only.

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?

With 75% schema coverage the baseline is 3, and the description earns above that by giving pricing semantics for `explain` ($0.50 adds a written explanation with source lines) and by explaining the x402 `payment` handshake (omit it to receive terms). The `holderWallet` discount path is left entirely to the schema description, so not everything is covered.

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?

The description names a specific verb and resource — inspecting a Uniswap v4 hook on Ethereum — and enumerates exactly what is returned: permission bits, implemented callbacks, fee logic and recipients, owner/admin functions with caps, upgradeability, and known templates. This is far more specific than the sibling hook_flags, which reads as a flags-only lookup, so an agent can tell them apart without opening either schema.

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?

It states the triggering situation explicitly: before trading or providing liquidity through a hook, when the agent needs to know what the hook can do. That is a clear use context, but it never names the alternative (hook_flags) or excludes cases such as non-Ethereum chains or non-v4 hooks.

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

All NIGHTSHIFT public toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources