Skip to main content
Glama
Sign In

FinzData market data

by io.github.FinzData
OverviewDiscussionsAdmin

Re-run a listed strategy

run_strategy
Idempotent

Answers 'how has this published strategy done since it started?' Give a slug from list_strategies; optionally end (default today). Returns stats, benchmark stats, equity curve, the published spec and the strategy page, re-running the strategy exactly as published on its full point-in-time history. Free on every tier, no API key needed. To change parameters use fork_strategy; to test your own idea use run_backtest (free tier: last 12 months; full history with any purchase).

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": {
      "slug": "<slug>"
    },
    "name": "run_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoLast date to run through (YYYY-MM-DD). Default today.
slugYesStrategy slug from list_strategies.
as_ofNoPoint-in-time cutoff (YYYY-MM-DD). Nothing dated after this is returned, preventing look-ahead bias. Defaults to today (UTC).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, idempotent=true, destructiveHint=false, so the description usefully adds the cost/access model ('free on every tier, no API key needed'), the exact-replay guarantee ('exactly as published on its full point-in-time history'), and the shape of the payload. It does not cover runtime/expense of a full-history re-run or failure behavior for an unknown slug, which keeps it from a 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?

Four dense sentences, with the purpose and the required input first, followed by return contents and then alternatives. Every sentence carries information, though the lead-in question phrasing is slightly less direct than a plain statement of the operation.

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?

With no output schema, the description compensates by enumerating the returned artifacts (stats, benchmark stats, equity curve, published spec, page). For a 3-parameter read-style computation it is nearly complete; only failure modes and re-run cost are unaddressed.

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?

Schema description coverage is 100%, so slug, end, and as_of are already documented including their defaults. The description reinforces the slug's source and the end default but adds no new semantics (e.g., date format constraints or interaction between end and as_of) beyond the schema, so the baseline 3 applies.

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 opens with a concrete question it answers ('how has this published strategy done since it started?') and states the operation precisely: re-running a published strategy on its full point-in-time history and returning stats, benchmark stats, equity curve, spec, and page. It is clearly distinguishable from fork_strategy (changing parameters) and run_backtest (own ideas).

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 names the prerequisite (a slug from list_strategies) and explicitly routes the agent to alternatives with the selecting condition: fork_strategy to change parameters, run_backtest to test your own idea. Exclusions and the free-tier limitation of run_backtest are stated, leaving little to inference.

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

All FinzData market data 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