AgentFeed

Tokenized stock peg

get_peg_deviation

Read-onlyIdempotent

Tokenized stock peg deviation on Solana: the on-chain DEX price of a tokenized US equity versus the underlying's last real trade, in bps, with 24h stats split into market-open and off-hours. Sampled every 5 minutes by our own collector; the token price is read on-chain. latest.reference is null: the underlying's reference price is not returned (its source does not allow redistribution), only the deviation computed from it. Costs 0.02 USDC per call (x402, USDC on Solana, Base, Polygon, Arbitrum or Arc).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`hours`	No	lookback 1-168, default 24
`symbol`	Yes	Tokenized equity symbol e.g. CRCLx, MSTRx, COINx

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	the get_peg_deviation payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_peg_deviation
`tool`	Yes	the tool that produced this payload

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": {},
+      "description": "the get_peg_deviation payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_peg_deviation",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_peg_deviation",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the read-only/idempotent/openWorld annotations: it discloses sampling cadence (every 5 minutes), data provenance (token price read on-chain by our own collector), a key data caveat (latest.reference is null because the underlying source forbids redistribution), and a per-call payment requirement with accepted chains. These are exactly the operational traits an agent cannot get from annotations or schema.

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 purpose in the first clause before the qualifications, and every clause carries real information (unit, cadence, null caveat, cost). It is dense and could be split for readability, but there is no filler.

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?

With an output schema present, return values needn't be explained, and the description still pre-empts a likely confusion by flagging that latest.reference comes back null. Cadence, provenance, unit, and cost are all covered, leaving nothing an agent needs to call it correctly.

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% and both params (symbol with examples, hours 1-168 default 24) are documented in the schema, so the description need not restate them. It adds no syntax or format detail beyond the schema, so baseline 3 applies; it does implicitly confirm the symbol refers to tokenized equities.

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+resource ('peg deviation'), names the counterparties being compared (on-chain DEX price of a tokenized US equity vs the underlying's last real trade), and specifies the unit (bps). An agent can distinguish this from sibling peg tools (get_peg_sessions, get_peg_universe) and from get_equity_24h.

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 context is implied: it's a Solana tokenized-equity deviation metric, and the cost line signals a paid call to be used deliberately. However, it never states when to prefer this over the obvious siblings (get_peg_sessions, get_peg_universe, get_equity_24h), so routing remains an inference.

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

All AgentFeed 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.