Stratify

build_report

Creates a shareable report page for a backtest the user owns and returns its URL. The page carries the honesty panel, equity and drawdown curves, walk-forward folds, the gross-to-net breakdown, a month grid and the trade table, computed from the stored backtest. Use when the user asks for a report or something to share.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`format`	No	'link' (default) returns the hosted URL of the report page. 'artifact' returns the whole self-contained HTML document as well, which costs considerably more tokens. 'full' builds the full strategy report and returns its link: the strategy's rules in plain English, what it did to a given capital, every trade plotted on a zoomable NIFTY chart, the evidence panel and the capital curve. 'full' is rate limited.	link
`capital`	No	format 'full' only. Starting capital in rupees. It sets the report's OPENING view — the reader can change it in the page without a new report. Default 1,000,000.
`risk_pct`	No	format 'full' only. Size by RISK instead of margin: the percent of capital the trade is allowed to lose in its worst case (2 means 'risk 2% per trade'). Only works where the position has a bounded worst case — a naked short does not, and the call is refused with that reason rather than sized off a guess. Overrides deploy_pct.
`deploy_pct`	No	format 'full' only. Percent of capital used as margin on any one trade. Default 10.
`backtest_id`	Yes	From a previous run_backtest.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`bytes`	No
`message`	No
`contains`	No
`document`	No
`mime_type`	No
`report_url`	No
`backtest_id`	No
`document_properties`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 25, 2026

addedInput schema / properties / format / default
```
Added value: +"link"
```

changedInput schema / properties / format / description

Previous value: -"'artifact' (default) returns the whole document to publish. 'link' returns only the hosted URL — far cheaper in tokens, and the right choice when the user just wants to look at it rather than keep it. 'full' builds the FULL STRATEGY REPORT and returns its link: the strategy's rules in plain English, what it did to ₹10 lakh of capital, every trade plotted on a zoomable NIFTY chart, the evidence panel, and the capital curve. Ask for it whenever someone wants to really understand a strategy rather than glance at it. It is rate limited."New value: +"'link' (default) returns the hosted URL of the report page. 'artifact' returns the whole self-contained HTML document as well, which costs considerably more tokens. 'full' builds the full strategy report and returns its link: the strategy's rules in plain English, what it did to a given capital, every trade plotted on a zoomable NIFTY chart, the evidence panel and the capital curve. 'full' is rate limited."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "backtest_id": {
+      "type": "string"
+    },
+    "bytes": {
+      "type": "integer"
+    },
+    "contains": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "document": {
+      "type": "string"
+    },
+    "document_properties": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "message": {
+      "type": "string"
+    },
+    "mime_type": {
+      "type": "string"
+    },
+    "report_url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedSep 16, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description goes beyond annotations (readOnlyHint=false, destructiveHint=false) by disclosing that it creates a resource, returns a URL, mentions token costs for 'artifact', rate limiting for 'full', and refusal conditions for risky risk_pct calls. It also explains the report's interactive nature (user can change capital view). No contradictions with annotations.

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 sentences with zero waste. The first sentence front-loads the core action and output, and the second gives the usage trigger. No redundant details.

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?

With an output schema present, the description needn't explain return values. It covers the report contents, ownership requirement, format options (via schema), and error conditions (via schema). It is complete for an agent to invoke correctly.

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 each parameter is well-documented in the schema. The tool description adds no additional parameter semantics beyond what the schema already provides. Baseline 3 is appropriate given full schema coverage.

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 verb+resource: 'Creates a shareable report page for a backtest the user owns and returns its URL.' It clearly differentiates from siblings like get_backtest (which retrieves data) and run_backtest (which executes a backtest) by focusing on the report generation action.

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 description explicitly says 'Use when the user asks for a report or something to share,' providing a clear when-to-use trigger. It does not name alternatives explicitly, but the context of siblings and the 'Use when' condition is sufficient for an agent to route correctly.

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

All Stratify tools Inspect

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

Need Help?