Agent Utils (x402)

by dev.workers.revenue-agent-jw.agent-utils-x402-production

Solana pre-promo covered-shelf aggregates vs matched null

solana_pre_promo

Read-onlyIdempotent

Pre-promo tape lookup for a Solana token when we hold a locked [-60m,0] window around its DexScreener paid-promo timestamp (specialty covered shelf). Returns raw aggregates: net buy USD, unique buyers, largest buyer share, and the same vs a matched-null mean from other covered tokens. Uncovered token: 404 with coverage:false, never fabricated. Free probe: GET /v0/solana/pre-promo-coverage. Not financial advice. PAID: $0.01 USDC per call on Base via x402 (MCP transport: retry with params._meta["x402/payment"]). Same tool over plain HTTP: GET /v1/solana/pre-promo.

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": {
      "token": "<token>"
    },
    "name": "solana_pre_promo"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes	Solana mint address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations only declare readOnly/idempotent/open-world; the description adds what they cannot: a $0.01 USDC per-call price on Base via x402, the MCP-specific retry path params._meta["x402/payment"], an alternate plain-HTTP endpoint, and an explicit no-fabrication contract with 404 + coverage:false for uncovered tokens. This is exactly the payment, error, and integrity context an agent needs before invoking a paid endpoint.

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?

Front-loaded with the operation and window semantics, then return fields, then error behavior, then payment mechanics — a sensible priority order. It is dense but nearly every clause carries operational weight; the 'Not financial advice' sentence is the only near-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?

With no output schema, the description carries the return-value burden and does list the aggregates (net buy USD, unique buyers, largest buyer share, matched-null mean). Payment, error, and fallback-transport details are all present; only response shape/pagination specifics for the aggregates are left implicit.

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?

The single token parameter is already fully documented in the schema as a base58 Solana mint address, so baseline would be 3. The description goes beyond the schema by disclosing the out-of-schema payment meta parameter (params._meta["x402/payment"]) required on retry, which is not represented in the input schema at all.

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 verb and resource: a pre-promo tape lookup for a Solana token against a locked [-60m,0] window around its DexScreener paid-promo timestamp, plus the exact aggregates returned. The parenthetical 'specialty covered shelf' and the matched-null comparison make the scope unmistakable, and no sibling operates in this domain.

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 a clear precondition for use (a locked window around a paid-promo timestamp must exist) and a free coverage-probe endpoint to check eligibility before spending money. It stops short of explicit 'do not use when' phrasing, but the 404/coverage:false branch effectively covers the negative case.

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

All Agent Utils (x402) tools Inspect

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

Need Help?