Skip to main content
Glama

draconic21 Daily Agent Signal + x402 Data Tools

by com.onrender.draconic21-x402-api
OverviewDiscussionsAdmin

Daily Agent Signal — single topic/id trace

signal_topic_trace
Read-onlyIdempotent

[PAID — 0.06 USDC on Base via x402] Use this when you follow one thread (one signal id) and want its path through every dated edition. Not when you want every thread's status at once (use signal_continuity) or a whole day's brief (signal_day). Deep appearance path for ONE topic or ONE signal id across every dated archive brief (dates, headlines, judgments, vs_prior, ranks) — cheaper than buying full history when you only care about one thread. Provide exactly one of topic or id. $0.06 USDC on Base, paid via x402 by the calling agent's own wallet. Call with no payment_header first to receive the payment requirements; your own wallet pays, never this server's.

Input Schema

NameRequiredDescriptionDefault
idNoA signal id to trace (from signal_latest or signal_continuity), e.g. 'catalog-concentration'. Provide this or topic, not both.
daysNoMost recent stored editions to search, 1-90 (default 90).
topicNoExact topic tag, e.g. 'x402'. Only the 2026-09-19..09-25 editions carry tags, so prefer id for current threads. Provide this or id, not both.
payment_headerNoOptional. Omit on your first call to receive the x402 payment challenge for free. After your own wallet/x402 client signs against that challenge, call this same tool again with the SAME business arguments plus this field set to the header your x402 client produced (typically { name: "PAYMENT-SIGNATURE", value: "<base64 payload>" }). This server never holds a wallet and never pays on your behalf.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"A signal id to trace (from signal_latest or signal_continuity), e.g. 'payai-head-relay402-8h-batch-rerank'. Provide this or topic, not both."New value: +"A signal id to trace (from signal_latest or signal_continuity), e.g. 'catalog-concentration'. Provide this or topic, not both."
  2. Changed3 schema fields changed
    • addedInput schema / properties / days
      Added value: +{
+  "description": "Most recent stored editions to search, 1-90 (default 90).",
+  "maximum": 90,
+  "minimum": 1,
+  "type": "integer"
+}
    • changedInput schema / properties / id / description
      Previous value: -"A specific signal id to trace, e.g. 'x402-http-402-rail'. Provide this or topic, not both."New value: +"A signal id to trace (from signal_latest or signal_continuity), e.g. 'payai-head-relay402-8h-batch-rerank'. Provide this or topic, not both."
    • changedInput schema / properties / topic / description
      Previous value: -"Free-text topic to trace, e.g. 'x402'. Provide this or id, not both."New value: +"Exact topic tag, e.g. 'x402'. Only the 2026-09-19..09-25 editions carry tags, so prefer id for current threads. Provide this or id, not both."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/openWorld annotations by disclosing the x402 payment protocol: a free first call with no payment_header to receive the challenge, then a re-call with the signed header paying 0.06 USDC from the caller's own wallet. This two-step payment flow is critical, non-obvious behavior not captured by any structured field.

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-loads the cost and the usage decision, and every sentence is functional. Slight redundancy in restating the 0.06 USDC / x402 / self-pay detail twice (bracketed tag and closing sentences) costs it a point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description enumerates the returned fields (dates, headlines, judgments, vs_prior, ranks) and fully explains the payment handshake. An agent has everything needed to call correctly, including the pay flow and return shape.

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%, so the schema already documents id, topic, days, and payment_header. The description reinforces the 'provide exactly one of topic or id' constraint but adds no syntax or format meaning beyond the schema, so the 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?

States a specific verb (trace) and resource (ONE topic or ONE signal id across every dated edition/brief), and explicitly contrasts itself with signal_continuity and signal_day. An agent can identify the tool without opening the schema.

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

Usage Guidelines5/5

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

Names both when to use (following one thread's path through every edition) and when not to, routing to specific siblings (signal_continuity for all-thread status, signal_day for a day's brief). Also adds a cost-based selection cue: cheaper than full history when you care about one thread.

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

All draconic21 Daily Agent Signal + x402 Data Tools 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