Skip to main content
Glama

cryptoport-port

by com.thecryptoport
OverviewDiscussionsAdmin

Stance arc as a dated series

stance_history
Read-only

FREE. The full stance arc for one ticker parsed into a dated series — one point per brief date with the movement (up / flat / down) — plus first and last brief, mention count and the flip flag. Derived from the published arc string; it is a parsed shape, not withheld data. Upstream briefs land on about 71% of days; board content is same-day roughly half the time and is never more than three days old. Not real-time. Every payload carries stale / stale_days / built_from_brief_date — read them. Commentary on public statements, not advice. This tool does not accept portfolio, position or risk-profile inputs and will refuse them with HTTP 400.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesTicker as published, e.g. SOL
paymentNoOptional x402 payment payload: the value you would send in the PAYMENT-SIGNATURE header (base64 JSON, x402 v2). Call without it first: the tool answers with the 402 terms and carries the verbatim PAYMENT-REQUIRED header value in `x402` — hand that to an x402 client to build the payload, which settles testnet USDC on Base Sepolia — then call again with this field. The receipt (tx_hash, payer, network) comes back in `settlement`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / payment / description
      Previous value: -"Optional x402 payment payload (the value you would put in the X-PAYMENT header, base64). Call without it first: the tool answers with the machine-readable 402 terms, you settle testnet USDC on Base Sepolia, then call again with this field."New value: +"Optional x402 payment payload: the value you would send in the PAYMENT-SIGNATURE header (base64 JSON, x402 v2). Call without it first: the tool answers with the 402 terms and carries the verbatim PAYMENT-REQUIRED header value in `x402` — hand that to an x402 client to build the payload, which settles testnet USDC on Base Sepolia — then call again with this field. The receipt (tx_hash, payer, network) comes back in `settlement`."
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description reveals data freshness limitations (not real-time, stale fields to read), derivation from the arc string, and coverage statistics (71% of days, same-day ~half the time). It also includes a disclaimer that it is commentary, not advice.

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 dense but well-structured, leading with the core purpose then layering data-quality and behavioral notes. Every sentence adds value, though it is slightly long and could be trimmed without losing information.

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?

With no output schema, the description explains the main return fields (dated series, movement, first/last brief, mention count, flip flag) and mentions staleness fields. It does not exhaustively list every field or the exact JSON shape, but it covers the essential contract for a caller.

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%, so the baseline is 3. The tool description does not add extra meaning to the ticker or payment parameters beyond what the schema already explains; it only adds a global note about rejected input types.

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 states a specific deliverable: the full stance arc for a ticker parsed into a dated series with movement, first/last brief, mention count, and flip flag. It is clearly distinguished from sibling tools by focusing on the stance arc rather than board snapshots, catalysts, or coin data.

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?

The description provides clear context—when you need a parsed stance arc—but does not explicitly name alternatives or state when not to use it. It does mention a hard constraint (rejects portfolio/position/risk inputs), which guides appropriate use.

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

All cryptoport-port toolsInspect
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.

Resources