Agent Decision & Evidence Tools (MCP + x402)

Signed coin-positioning brief

coin_positioning_brief

Read-only

Calculate a disclosed crowded-long/short score from current Hyperliquid funding and premium. The response also includes an at-least-two-exchange spot median, open interest, volume and the service's six-hour archive trend as separate context; a still-filling archive is labelled and does not enter this score.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbol`	No		BTC

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`perp`	No
`rule`	No
`spot`	No
`tool`	No
`as_of`	No
`error`	No
`trend`	No
`symbol`	No
`charged`	No	When present on an error, false means the failed result is uncharged.
`message`	No
`missing`	No
`receipt`	No
`settled`	No	When present on an error, false means no settlement occurred.
`unknown`	No
`accepted`	No
`evidence`	No
`retryable`	No
`error_code`	No
`extensions`	No
`positioning`	No
`status_code`	No
`did_you_mean`	No
`missing_checks`	No
`partial_evidence`	No
`positioning_score`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 6, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
removedInput schema / properties / symbol / title
```
Removed value: -"Symbol"
```

removedInput schema / title

Removed value: -"coin_positioning_brief_toolArguments"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "anyOf": [
+    {
+      "required": [
+        "symbol",
+        "as_of",
+        "positioning_score",
+        "positioning",
+        "spot",
+        "perp",
+        "trend",
+        "evidence",
+        "missing_checks",
+        "rule",
+        "note",
+        "receipt",
+        "extensions"
+      ]
+    },
+    {
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "description": "Structured result contract for coin_positioning_brief. A success satisfies the documented success branch. A domain or tool error includes error and is not a successful settlement; unpaid x402 requirements are carried by the transport wrapper.",
+  "properties": {
+    "accepted": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "as_of": {
+      "type": "string"
+    },
+    "charged": {
+      "description": "When present on an error, false means the failed result is uncharged.",
+      "type": "boolean"
+    },
+    "did_you_mean": {
+      "additionalProperties": true,
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "error": {
+      "oneOf": [
+        {
+          "type": "string"
+        },
+        {
+          "additionalProperties": true,
+          "properties": {
+            "code": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "message": {
+              "type": "string"
+            },
+            "param": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "type": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "message"
+          ],
+          "type": "object"
+        }
+      ]
+    },
+    "error_code": {
+      "type": "string"
+    },
+    "evidence": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "extensions": {
+      "additionalProperties": true,
+      "properties": {
+        "delivery-receipt": {
+          "additionalProperties": true,
+          "properties": {
+            "how_to_verify": {
+              "type": "string"
+            },
+            "issued_at": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "issuer": {
+              "type": "string"
+            },
+            "issuer_key": {
+              "type": "string"
+            },
+            "key_id": {
+              "type": "string"
+            },
+            "result_hash": {
+              "type": "string"
+            },
+            "service": {
+              "type": "string"
+            },
+            "signature": {
+              "type": "string"
+            },
+            "signed_message": {
+              "type": "string"
+            },
+            "standard": {
+              "const": "eucompliance-receipt/2",
+              "type": "string"
+            },
+            "subject": {
+              "type": "string"
+            },
+            "valid_until": {
+              "format": "date-time",
+              "type": "string"
+            },
+            "verify_url": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "standard",
+            "service",
+            "subject",
+            "result_hash",
+            "issued_at",
+            "valid_until",
+            "issuer",
+            "issuer_key",
+            "key_id",
+            "verify_url",
+            "how_to_verify",
+            "signature",
+            "signed_message"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "delivery-receipt"
+      ],
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "missing": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "missing_checks": {
+      "items": {},
+      "type": "array"
+    },
+    "note": {
+      "type": "string"
+    },
+    "partial_evidence": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "perp": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "positioning": {
+      "type": "string"
+    },
+    "positioning_score": {
+      "type": "integer"
+    },
+    "receipt": {
+      "additionalProperties": true,
+      "properties": {
+        "how_to_verify": {
+          "type": "string"
+        },
+        "issued_at": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "issuer": {
+          "type": "string"
+        },
+        "issuer_key": {
+          "type": "string"
+        },
+        "key_id": {
+          "type": "string"
+        },
+        "result_hash": {
+          "type": "string"
+        },
+        "service": {
+          "type": "string"
+        },
+        "signature": {
+          "type": "string"
+        },
+        "signed_message": {
+          "type": "string"
+        },
+        "standard": {
+          "const": "eucompliance-receipt/2",
+          "type": "string"
+        },
+        "subject": {
+          "type": "string"
+        },
+        "valid_until": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "verify_url": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "standard",
+        "service",
+        "subject",
+        "result_hash",
+        "issued_at",
+        "valid_until",
+        "issuer",
+        "issuer_key",
+        "key_id",
+        "verify_url",
+        "how_to_verify",
+        "signature",
+        "signed_message"
+      ],
+      "type": "object"
+    },
+    "retryable": {
+      "type": "boolean"
+    },
+    "rule": {
+      "type": "string"
+    },
+    "settled": {
+      "description": "When present on an error, false means no settlement occurred.",
+      "type": "boolean"
+    },
+    "spot": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "status_code": {
+      "type": "integer"
+    },
+    "symbol": {
+      "type": "string"
+    },
+    "tool": {
+      "type": "string"
+    },
+    "trend": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "unknown": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

AddedSep 6, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already signal read-only and non-destructive behavior. The description adds useful behavioral context beyond annotations: the response separates the score from extra context, mentions multi-exchange median aggregation, and explicitly states that a still-filling archive is labelled and excluded from the score. No contradiction with annotations exists.

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?

The description is compact and front-loads the main purpose, with no filler. However, its single long sentence with multiple embedded clauses, especially the archive caveat, is somewhat dense and could be more readable if split into two sentences.

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

Completeness4/5

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

Given that an output schema exists and the tool has only one optional parameter, the description covers the core calculation, included output context, and an important edge case about the filling archive. It is mostly complete, with the only notable gap being the lack of explicit symbol guidance.

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

Parameters2/5

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

Schema coverage is 0% for the single symbol parameter, and the description does not mention the parameter at all. The parameter name 'symbol' is self-explanatory, but the description fails to compensate for the low schema coverage, leaving the agent without explicit guidance on what values are accepted or how the symbol relates to the calculation.

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 opens with a specific verb and resource: 'Calculate a disclosed crowded-long/short score from current Hyperliquid funding and premium.' This is clearly distinct from generic market-data siblings like market_data, perp_market_data, or spot_price, so an agent can tell this tool's unique purpose.

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 about when to choose this tool over alternatives, nor are any exclusions or sibling references provided. The intended usage is only implied by the purpose statement, leaving the agent to infer when a crowded-positioning brief is preferred over other market-data tools.

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

All Agent Decision & Evidence Tools (MCP + x402) tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.