AgentFeed

Peg by session

get_peg_sessions

Read-onlyIdempotent

Tokenized stock peg by trading session: deviation broken out across open, premarket, afterhours, overnight and weekend — mean, p95, max bps and median liquidity each, with the worst off-hours window flagged. Market-open acts as the control. Costs 0.03 USDC per call (x402, USDC on Solana or Base).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`days`	No	lookback 1-30, default 7
`symbol`	Yes	Tokenized equity symbol e.g. CRCLx, MSTRx, COINx

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes	the get_peg_sessions payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_peg_sessions
`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_sessions payload; a real captured example is free at https://x402.ochinimus.app/api/sample/get_peg_sessions",
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "tool": {
+      "const": "get_peg_sessions",
+      "description": "the tool that produced this payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "tool",
+    "data"
+  ],
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, idempotent, non-destructive), so no caveats are needed there. The description adds important supplementary behavior: a 0.03 USDC per-call cost paid via x402 on Solana or Base, and the flagging of the worst off-hours window. No contradiction with annotations.

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 compact and front-loaded: the core session breakdown appears first, followed by the control definition and pricing in a few short sentences. Every sentence adds distinct value with no filler or repetition.

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 only two parameters, fully covered schema descriptions, and an output schema present, the description supplies the remaining essential context: session categories, metric types, the market-open control, and paid-call behavior. Nothing critical is missing for correct invocation.

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%: symbol and days are already documented with format, range, and default. The tool description adds no extra parameter-level meaning, so the baseline of 3 is appropriate.

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?

The description clearly identifies the tool as providing tokenized-equity peg deviation statistics broken out by trading session (open, premarket, afterhours, overnight, weekend), with specific metrics enumerated. This distinguishes it from sibling tools like get_peg_deviation and get_peg_universe, even without naming them explicitly.

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?

It gives clear context for when to use this tool: when session-level peg deviation, off-hours comparison, and the worst off-hours window are needed, with market-open as the control. It does not explicitly name alternatives or state when not to use it, so it falls short of a 5 but is well beyond no guidance.

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.