Skip to main content
Glama

Backtesting Arena

by io.github.Schoasch
OverviewDiscussionsAdmin

Get On-Chain Series Latest Value

arena_get_onchain_latest

What does this on-chain metric read right now? Returns the most recent value of ONE on-chain series from the Bitcoin Research Kit as { series_id, metric_name, date, value }. Cheapest way to answer "what is X right now" (MVRV, SOPR, realized price, hash rate, …). Discover valid series_ids with arena_list_onchain_series; for the history behind the number use arena_get_onchain_history. A single reading has no context — pair it with the series percentile before calling any level high or low. [Free tier]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
series_idYesBRK series id, e.g. 'mvrv', 'sopr', 'realized_price'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / context
      Removed value: -{
-  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "series_id",
-  "context"
-]New value: +[
+  "series_id"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool returns a single reading, notes it has no context ('A single reading has no context') and advises pairing with the series percentile, and hints at cost with '[Free tier]' and 'Cheapest way'. While it doesn't explicitly say 'read-only' or cover error behavior, the description provides substantial operational context beyond the bare function.

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 front-loaded with the core purpose and output format, then adds practical guidance (alternatives, context warning, free tier) in a compact set of sentences. Every sentence earns its place: the opening question captures intent, the return format is explicit, and the caveat prevents misuse. It is dense but not bloated.

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?

The tool is simple (1 parameter, no output schema), and the description covers everything an agent needs: the return shape, how to discover valid inputs, the relationship to history, and a usage pitfall (single reading lacks context). Since there is no output schema, the explicit field list is essential and provided. Nothing critical is missing.

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 schema already covers the parameter with examples ('mvrv', 'sopr', 'realized_price'), so baseline is 3. The description adds value by explaining that series_ids come from a separate listing tool and by reiterating the output fields, which clarifies how to interpret the response. This goes beyond merely restating the schema and compensates slightly for the lack of an output 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 states a specific action ('Returns the most recent value of ONE on-chain series') with a concrete output format and examples ('MVRV, SOPR, realized price, hash rate'). It clearly distinguishes itself from arena_get_onchain_history by contrast, and names the discovery tool arena_list_onchain_series. The purpose is unambiguous and immediately separates it from dozens of siblings.

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

Usage Guidelines5/5

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

It explicitly frames the tool as 'Cheapest way to answer "what is X right now"' and gives direct alternatives: 'for the history behind the number use arena_get_onchain_history' and 'Discover valid series_ids with arena_list_onchain_series'. This tells the agent exactly when to use this tool versus its siblings, leaving nothing to inference.

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

All Backtesting Arena 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