Skip to main content
Glama

CryptoSocials

by net.cryptosocials.api
OverviewDiscussionsAdmin

Get market history

get_market_history
Read-only

Use when investigating the price timeline around posts or assessing a claim against later prices. Read one stored price series from returned post price context or list_market_series. Omit interval for raw points, or choose an advertised candle interval to include candles and related posts. point_summary explicitly identifies its entire requested time window, which may include prices before a selected post; restrict the window to published_at or later for a post outcome. Raw points continue with next_point_cursor until null, independently of candle next_cursor. Gaps remain explicit; no live quote or exact post-time price is implied.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size: an integer from 1 to 50, default 20. Read additional pages with the returned cursor and unchanged query/page size.
cursorNoPass the returned next_cursor unchanged to the same tool and connection with the original query arguments. For post searches preserve exact UTC dates, filters, order, limit, projection and mode. Omit cursor to start a new or changed query.
date_toYes
asset_idYes
intervalNoOptional; choose an advertised interval for candles. Omit for raw points only.
date_fromYes
series_idYes
point_onlyNoRead raw points without candles or related posts. Omission of interval has the same effect.
point_limitNo
point_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Page size: an integer from 1 to 50, default 20. Read additional pages with the returned cursor and unchanged query/page size."
  2. Changed1 schema field changed
    • addedInput schema / properties / cursor / description
      Added value: +"Pass the returned next_cursor unchanged to the same tool and connection with the original query arguments. For post searches preserve exact UTC dates, filters, order, limit, projection and mode. Omit cursor to start a new or changed query."
  3. Changed4 schema fields changed
    • changedInput schema / properties / interval / description
      Previous value: -"Required for candles. Omit only when point_only=true."New value: +"Optional; choose an advertised interval for candles. Omit for raw points only."
    • changedInput schema / properties / point_limit / default
      Previous value: -100New value: +250
    • removedInput schema / properties / point_only / default
      Removed value: -false
    • addedInput schema / properties / point_only / description
      Added value: +"Read raw points without candles or related posts. Omission of interval has the same effect."
  4. Changed3 schema fields changed
    • addedInput schema / properties / interval / description
      Added value: +"Required for candles. Omit only when point_only=true."
    • changedInput schema / properties / interval / enum
      Previous value: -[
-  300,
-  900,
-  3600,
-  86400
-]New value: +[
+  60,
+  300,
+  900,
+  3600,
+  86400
+]
    • changedInput schema / required
      Previous value: -[
-  "asset_id",
-  "series_id",
-  "date_from",
-  "date_to",
-  "interval"
-]New value: +[
+  "asset_id",
+  "series_id",
+  "date_from",
+  "date_to"
+]
  5. Changed3 schema fields changed
    • addedInput schema / properties / point_cursor
      Added value: +{
+  "maxLength": 2048,
+  "type": "string"
+}
    • addedInput schema / properties / point_limit
      Added value: +{
+  "default": 100,
+  "maximum": 250,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / point_only
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
  6. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/destructive/openWorld/idempotent, and the description goes well beyond them: raw points paginate via next_point_cursor until null independently of the candle next_cursor, gaps are explicit, and no live quote or exact post-time price is implied. These are exactly the non-obvious traits an agent needs before calling.

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?

Usage grounds are front-loaded and each sentence carries information (windowing caveat, pagination rule, gap disclosure). It is dense and slightly cryptic in places ('point_summary explicitly identifies its entire requested time window') but wastes little.

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?

For a 10-parameter, no-output-schema read tool with a 40%-covered schema, the description supplies the missing behavioral context: pagination independence, explicit gaps, window semantics, and no implied live pricing. Date-range and required-ID semantics remain thin, but the agent has enough to call it correctly.

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?

Schema coverage is only 40% across 10 params, so the description must compensate, and it does for the trickiest ones: omitting interval yields raw points while choosing an advertised interval adds candles and related posts, and it disambiguates the two independent cursors (next_point_cursor vs next_cursor). It leaves asset_id/series_id/date_from/date_to semantics largely to the schema, hence not a 5.

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 states a specific verb and resource ('Read one stored price series') and distinguishes itself from the sibling list_market_series by pointing at it as the source of series_id. It's clear an agent reads a single series rather than enumerating them, though the contrast with list_market_series is implied rather than spelled out.

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 opens with explicit usage context ('investigating the price timeline around posts or assessing a claim against later prices') and even gives scenario-specific configuration, e.g. restricting the window to published_at or later for a post outcome. No explicit when-not or exclusion is stated, so it falls just short of a 5.

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

All CryptoSocials 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