Flexreport Finance

get_strategy_performance_summary

Read-only

Leaderboard of since-inception performance vs the S&P 500 for all strategy books.

THE first stop for "how are the stock picks / strategies performing?". Returns
`strategies`, one headline row per book — the four strategies plus the pooled optimized book — sorted
by excess return over the S&P 500: {strategy_name, display_name, inception_date,
since_inception_return, sp_since_inception, excess_since_inception,
annualized_return, max_drawdown, sharpe, sp_sharpe, ytd_return, growth_strategy,
growth_sp, days_tracked}.

growth_strategy / growth_sp = what `amount` invested at inception would be worth in
the strategy vs the S&P 500.

Drill into one book's full daily series with `get_strategy_track_record`, or its
per-trade adds/drops with `get_strategy_swaps`.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`amount`	No	Dollar amount assumed invested at inception; scales growth_strategy / growth_sp.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`strategies`	Yes	One row per book with history, sorted by excess_since_inception (best first).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: the sort key (excess return over the S&P 500), the one-row-per-book granularity, and the meaning of growth_strategy/growth_sp as the value of `amount` invested at inception.

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 one-line purpose and the headline use case, then supporting detail. The inline enumeration of twelve return fields is somewhat long, but it is the tool's actual payload and each remaining sentence earns its place.

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?

The tool returns a single flat table with one parameter and an output schema, so almost nothing is left to infer: purpose, sorting, row shape, and drill-down paths are all stated. The field list partially duplicates the output schema, which keeps it just short of a 5.

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% and the `amount` param already documents 'dollar amount assumed invested at inception; scales growth_strategy / growth_sp'. The description's explanation of growth_strategy/growth_sp restates that same semantics, so it adds little beyond the schema — baseline 3.

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?

Opens with a specific verb+resource+scope: a since-inception performance leaderboard versus the S&P 500 across all strategy books. It also explicitly distinguishes itself from siblings get_strategy_track_record and get_strategy_swaps, so an agent can route without opening a schema.

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?

'THE first stop for "how are the stock picks / strategies performing?"' gives an explicit entry-point condition, and the closing sentences name the two alternatives with the conditions that select them (full daily series vs per-trade adds/drops).

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

All Flexreport Finance 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?