AgentFeed

SOL and BTC positioning

get_positioning

Read-onlyIdempotent

SOL+BTC positioning: long/short account ratio (retail crowding) + open interest with 1h/24h change (Bybit). Costs 0.004 USDC per call (x402, USDC on Solana or Base).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

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

First observedSep 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds valuable behavioral context beyond this: the exact data mix, the 1h/24h change windows, the Bybit venue, and a transparent cost of 0.004 USDC per call via x402 on Solana or Base. This is useful operational information an agent needs before invoking.

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 two compact sentences with no filler. The core data and venue are front-loaded, and the cost/payment detail is added as a final, clearly separable clause. Every part earns its place.

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?

For a zero-parameter read-only tool with an output schema, this description is complete. It names the assets, metrics, timeframes, venue, and cost. Since the output schema exists, the description does not need to explain return values, and no additional selection criteria or prerequisites are required to invoke it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is no parameter semantics for the description to clarify. The baseline of 4 applies because no parameter documentation burden exists; the description instead focuses on what data is returned and at what cost.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is specific about what the tool returns: SOL and BTC long/short account ratio and open interest with 1h/24h changes on Bybit. It does not use an explicit verb like 'retrieves' or 'returns', but the resource, venue, and metrics are unambiguous. It is distinguishable from siblings like get_open_interest and get_long_short mostly by its combined scope, though it does not explicitly call out those alternatives.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives. Sibling tools such as get_long_short, get_open_interest, get_oi_spike_scan, and get_funding_rate cover overlapping concepts, and the description does not state when positioning is preferable or how it differs. Usage is only implied by the tool name and title.

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.