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, Base, Polygon, Arbitrum or Arc).

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/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, covering the safety profile. The description adds genuinely new operational context: the 0.03 USDC x402 charge and the accepted payment chains (Solana, Base, Polygon, Arbitrum, Arc), plus the specific statistics returned and the flagged worst off-hours window.

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?

A single dense sentence with the headline (peg by session) front-loaded, followed by the breakdown and then the cost caveat. Every clause carries information, though the em-dash chain of sessions and measures is heavy for one sentence.

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, the description doesn't need to enumerate return values, yet it still names the key measures and the control baseline, and it discloses the paid-call requirement. Nothing an agent needs to decide or invoke correctly is missing.

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 parameters are documented inline (days lookback 1-30 default 7; symbol format e.g. CRCLx). The description adds no parameter-level detail at all, so the baseline 3 applies when the schema does all the work.

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 the resource (tokenized stock peg) and the exact analytic cut (deviation broken out across open, premarket, afterhours, overnight, weekend) with the output measures named. This session-level breakout is what separates it from siblings like get_peg_deviation and get_peg_universe, so an agent can pick it without opening a schema.

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?

It implicitly signals when session granularity matters by describing the off-hours breakdown and noting 'Market-open acts as the control,' which tells the agent how to read the result. However, it never states when to prefer this over get_peg_deviation or get_peg_universe, nor any prerequisites beyond the cost line.

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.