Skip to main content
Glama

Backtesting Arena

by io.github.Schoasch
OverviewDiscussionsAdmin

Get Arena Pulse Today

arena_get_pulse

How hot is the Bitcoin market today? Daily 0-100 heat score for the Bitcoin market, aggregated from 8 components (BTC-Cycle, F&G, Altcoin-Season, Bullmarket-Ampel, Funding-Rate, Hash-Ribbons, Mayer-Multiple, MVRV-Z). Returns score, band label, color, 7d/30d delta, verdict, components breakdown, plus score_percentile ranking today’s score against its own history (e.g. 42 = 44th percentile — how hot/cold vs history, not just the raw number). score_semantics says which value you hold: the daily snapshot frozen once a day by the cron, or — before that cron has run for today — a live preliminary that still moves and whose percentile/deltas compare against frozen snapshots. band_driver names the number the band follows. Pass fields="full" for drivers[]: each component with value, weight, contribution (they add up to the score) and percentile_rank against its own history. [Free tier]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoOmit for the default response. 'full' adds `drivers[]` — each component with value, weight, contribution (the contributions add up to the headline score), percentile_rank against its own stored history (expanding, with basis and n) — plus drivers_note with the exact arithmetic.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Omit for the default response. 'full' adds `drivers[]` — each component with value, weight, contribution (the contributions add up to the headline score), percentile_rank against its own stored history (expanding, with basis and n) — plus drivers_note with the exact arithmetic.",
+  "enum": [
+    "full"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • 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"
-}
    • removedInput schema / required
      Removed value: -[
-  "context"
-]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it explains score_semantics (frozen daily snapshot vs. live preliminary that still moves), how percentile/deltas compare against frozen snapshots, and band_driver. It never explicitly states it is a read-only/free operation aside from the '[Free tier]' tag, and omits auth/rate-limit context, keeping it just below 5.

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?

Front-loaded with the core purpose and key output fields, and every clause contributes information rather than padding. It is somewhat long and presented as a single dense paragraph, which slightly reduces scannability, but it is efficient overall.

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?

No output schema exists, so the description must describe the return payload, and it does so comprehensively: score, band label, color, 7d/30d delta, verdict, components breakdown, score_percentile, band_driver, and the opt-in drivers[]. Nothing an agent needs to interpret results is missing.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents fields='full'. The description restates the drivers[] contents and adds the arithmetic framing ('contributions add up to the headline score'), which is mild added value. Baseline 3 applies when the schema does the heavy lifting.

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?

States a highly specific resource and scope: a daily 0-100 heat score for the Bitcoin market, and enumerates the 8 named components it aggregates (BTC-Cycle, F&G, Altcoin-Season, etc.), which implicitly distinguishes this composite from the individual component sibling tools. An agent can tell what this returns without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied by the 'how hot is the Bitcoin market today?' framing and the composite nature, but there is no explicit when-to-use, when-not, or named alternative (e.g. vs arena_get_cycle or arena_get_fear_greed). The only direct instruction is the fields='full' opt-in, which is a parameter hint rather than selection guidance.

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