Sera MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

get_coin_history

Retrieve historical price data for a stablecoin. Returns timestamp and price pairs for sparklines or charts, with configurable days.

Instructions

Get historical price data for a specific stablecoin. Returns timestamp and price pairs suitable for sparklines or charts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "get_coin_history"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	Number of days of history (1-365). Default: 7
`ticker`	Yes	The coin ticker symbol (e.g., USDT, USDC). Case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 3, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states the return format ('timestamp and price pairs') but does not elaborate on other aspects like data source, rate limits, or handling of non-stablecoin tickers. This is adequate for a simple read operation but not rich.

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 a single, succinct sentence that directly states the function, scope, and output. Every word earns its place, with no redundancy or filler.

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 simple read tool with only two parameters, the description covers the essential purpose and output format, and the schema handles parameter details. It lacks explicit sibling differentiation and a detailed output structure, but overall it is sufficiently complete for an agent to select and invoke the tool.

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?

The input schema already fully describes both parameters (ticker and days) with 100% coverage. The description adds no new parameter semantics beyond reinforcing the stablecoin scope, so it does not improve on the schema.

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 uses a specific verb ('Get'), identifies the resource ('historical price data'), and scopes it to 'a specific stablecoin.' This clearly distinguishes it from sibling tools like get_market or get_coin_metadata by emphasizing the historical aspect.

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 phrase 'suitable for sparklines or charts' provides a clear usage context, indicating when this tool is appropriate. However, it does not explicitly name alternative tools or state when not to use it, slightly limiting the guidance.

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