Skip to main content
Glama

Neutrino Strategy-Check & DeFi Data (AI-operated)

Strategy validation (free demo)

validate_strategy_demo
Read-onlyIdempotent

Free demo of the paid strategy-validation check. Send periodic NET returns as decimals (0.01 = 1%); only the first 60 observations and 300 bootstrap resamples are used. Returns annualised Sharpe, block-bootstrap 95% CI, probabilistic and deflated Sharpe (corrects for n_trials), max drawdown, min track-record length and a verdict. Statistical diagnostic on supplied data, not investment advice.

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": {
      "returns": "<returns>"
    },
    "name": "validate_strategy_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault
returnsYesperiodic net returns as decimals
n_trialsNohonest count of strategy variants tried before picking this one
periods_per_yearNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/closed-world annotations, it discloses the silent truncation at 60 observations and 300 bootstrap resamples, that deflated Sharpe corrects for n_trials, the full set of returned statistics, and a 'not investment advice' disclaimer. These are exactly the behavioral traits an agent needs before invoking a statistical tool.

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?

Two tight sentences: the demo framing and input caps come first, the returned statistics second, and the disclaimer last. Nothing is repeated from the schema or annotations, and the output enumeration is dense but informative rather than 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?

With no output schema, the description compensates by naming every returned statistic and the verdict, and it documents the truncation behavior that materially affects results. The only gap is the undocumented periods_per_year parameter, which matters for annualisation and is left to the caller to infer.

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?

Schema coverage is 67% (returns and n_trials documented, periods_per_year not). The description reinforces the decimal convention for returns and, more importantly, explains that n_trials must be an 'honest count of variants tried' because deflated Sharpe corrects for it, adding rationale the schema only states flatly. periods_per_year remains unexplained in both places.

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 resource and operation: a free demo of a paid strategy-validation check, and enumerates exactly what is computed (annualised Sharpe, block-bootstrap CI, probabilistic/deflated Sharpe, max drawdown, min track record, verdict). It also explicitly frames itself as the demo counterpart of the paid check, which separates it from paid_api_terms and dataset_sample.

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 demo-vs-paid framing and the stated caps (first 60 observations, 300 resamples) tell an agent this is for a lightweight trial run rather than production validation. It stops short of explicitly saying when to escalate to the paid tool or what to do if the user needs more than 60 observations.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources