Skip to main content
Glama

Backtesting Arena

by io.github.Schoasch
OverviewDiscussionsAdmin

Get Stablecoin Supply Trend

arena_get_stablecoin_supply

Aggregate stablecoin supply (crypto-liquidity proxy) — is the liquidity impulse turning or accelerating? macro_regime only gives the 30d delta; this exposes the trend: current supply, 30d/90d change (USD + %) plus a daily time series (days, default 365; resolution states points and spacing) so direction and speed are visible, not just a single delta. Read impulse for what the supply change is doing — four states (accelerating / decelerating / reversal / flat). The neighbouring acceleration_usd is the signed difference last-30d minus prior-30d and gets LARGE exactly when the trend reverses, while the older boolean accelerating requires the same direction AND a bigger magnitude; a reversal therefore shows a big acceleration_usd next to accelerating: false. Source DefiLlama peggedUSD. [Free tier]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLength of the returned daily series in days. Default 365, clamped 7–1095.

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 / days
      Added value: +{
+  "description": "Length of the returned daily series in days. Default 365, clamped 7–1095.",
+  "type": "integer"
+}
  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.2/5.0
Behavior4/5

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

With no annotations, the description carries full behavioral burden and does well: it discloses the data source (DefiLlama peggedUSD), the free-tier status, and the structure of the returned trend (current supply plus 30d/90d change and a daily series). It explains tricky field semantics such as what `impulse` states mean, how `acceleration_usd` behaves on reversal, and why it can be large while `accelerating` is false. Return format is described at concept level, though exact response shape is left undefined since no output schema exists.

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 single paragraph is front-loaded with the tool's purpose and then elaborates on field interpretation. It is dense and information-rich without being repetitive; a minor deduction for packing several concepts (trend, impulse, acceleration_usd, accelerating) into a long sentence that could be split for scanability.

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?

Given one optional parameter, no annotations, no output schema, and a complex set of sibling tools, the description supplies enough conceptual guidance about returned fields and their interpretation to call and use the tool correctly. It remains slightly short of fully describing the response shape, but no output schema exists, so the conceptual description is reasonable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter exists and schema coverage is 100%, so baseline would be 3. The description goes beyond the schema by restating the default (365), the control over both points and spacing via `resolution`, and the effective meaning of `days` for the series length. That is real added value over the schema's clamp range.

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 ('Aggregate stablecoin supply') and explicitly differentiates itself from the sibling 'macro_regime,' which 'only gives the 30d delta.' This distinguishes scope and intent clearly. It stops just short of 5 because the routing language names one sibling but doesn't provide a positive selection rule across the broader toolset.

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 gives a clear context for use - determining whether the liquidity impulse is turning or accelerating - and explicitly contrasts the tool with arena_get_macro_regime as the alternative for a single 30d delta. There is no explicit 'when not to use,' but the comparative framing is strong enough to route an agent.

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