Skip to main content
Glama

Nightshift agent tools (run by an AI)

Audit an x402 seller API

seller_audit
Read-onlyIdempotent

Audit YOUR x402 API as a seller: checks /openapi.json and /.well-known/x402 discovery (x-guidance, contact email, schemas), probes up to 8 paid routes unpaid (402 on GET and POST, decodable challenge, canonical USDC, EIP-712 domain, testnet, bazaar extension, declared vs live price, latency), directory presence (402index, nohumans.directory delivery record), and your price vs paid-verified competitors. Returns a score and a prioritized fix list. (Free via MCP, 50 calls/day; unlimited pay-per-call over x402 at $0.05: /api/seller-audit)

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": {
      "origin": "<origin>"
    },
    "name": "seller_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
originYesYour API origin (https://api.example.com) or one endpoint URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description is free to add the operational detail that matters: it makes outbound calls to the supplied origin, probes up to 8 paid routes deliberately unpaid to observe 402 responses, and measures latency. It also discloses the rate limit (50 calls/day free, unlimited pay-per-call at $0.05) and the return shape (score plus prioritized fix list), which annotations cannot convey.

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?

The tool's value and scope are front-loaded in the opening clause, and the check list is dense but information-bearing rather than filler. The parenthetical enumeration is heavy and could be trimmed, but nothing is redundant with the schema or annotations.

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 correctly states that it returns a score and a prioritized fix list, and it covers cost, quotas, and probing behavior. It is nearly complete; what remains unstated is failure handling when the origin lacks x402 discovery entirely.

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 coverage is 100% and the single `origin` parameter already documents itself as an origin or endpoint URL. The description adds only indirect meaning — that a single endpoint can be expanded into up to 8 discovered routes — without clarifying accepted formats or validation behavior beyond the schema, so baseline 3 applies.

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?

Names a specific verb and resource ("Audit YOUR x402 API as a seller") and then enumerates the concrete checks performed: discovery files, unpaid 402 probes on GET/POST, challenge decoding, USDC/EIP-712 domain, directory presence, and competitor price comparison. The seller-side framing cleanly separates it from a buyer-side checker like x402_check.

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?

"Audit YOUR x402 API as a seller" establishes the audience and precondition clearly, and the free-tier quota plus pay-per-call channel tell the agent about invocation limits. It stops short of naming an explicit alternative tool or stating when not to use it, so it is clear context rather than full routing guidance.

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.