Skip to main content
Glama
Sign In

cortexcloud

by io.github.jonahthan433
OverviewDiscussionsAdmin

cortex_register_whale_webhook

Register an HTTPS webhook for whale-alert deliveries. Registration is x402 paid: $0.100 USDC on Base; each delivered alert accrues $0.02 on the registration. HMAC-SHA256 signed when 'secret' is supplied. List with GET /v1/webhooks/whale-alerts?owner=0x... (free), unregister with DELETE ?token=... (free).

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": {
      "url": "<url>",
      "address": "<address>"
    },
    "name": "cortex_register_whale_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesHTTPS endpoint that receives alert deliveries
chainNoChain: ethereum, base, arbitrum, polygon, optimismethereum
limitNo
secretNoOptional signing secret (enables HMAC-SHA256)
addressYesEVM wallet to watch (from or to)
min_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does disclose key traits: x402 payment cost ($0.100 USDC on Base), a $0.02 per-alert accrual, optional HMAC-SHA256 signing, and free list/unregister endpoints. It still omits auth/payment-header mechanics, response behavior, idempotency, and error handling for a mutation/payment tool.

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?

The description is front-loaded with the core action, then adds pricing, signing, and related free endpoints in four compact sentences. Every sentence contributes relevant information without 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?

For a paid mutation tool with no annotations and no output schema, the description provides useful pricing and signing context but remains incomplete. It does not explain how x402 payment is supplied, what the registration response contains (e.g., token), or operational details an agent would need before invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67%, and the description adds little beyond the schema: it repeats that `secret` enables HMAC-SHA256 and that `url` is an HTTPS endpoint. It does not explain the undocumented `limit` or `min_usd` parameters, nor does it add meaning for `chain` or `address` beyond the schema.

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 verb and resource: 'Register an HTTPS webhook for whale-alert deliveries.' It is clearly distinguished from the sibling read/aggregate tools by being the webhook-registration operation, though it does not explicitly name a sibling alternative.

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?

Usage is implied: it is for registering whale-alert webhooks, and it notes free HTTP endpoints for listing and unregistering. However, it does not explicitly say when to use this instead of polling `cortex_whale_alerts`, nor does it state prerequisites or exclusions.

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

All cortexcloud 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