Flexreport Finance

get_stock_picks

Read-only

Fetch the latest LLM-selected stock picks (current rebalance holdings).

Returns `picks`, the holdings selected for the most recent rebalance date — the names
the backend's strategies are currently positioned in. Each pick is a record (ticker,
strategy, weight, rebalance date, and related fields; values are strings).
Synchronous and read-only — no auth required.

Each holding also carries a CURRENT-BASKET YTD view: `ytd_return` (that stock's
Jan 1 -> now price return) and the strategy-level weighted `basket_ytd_return`.
For how the strategies have ACTUALLY performed since inception (the realized track
record of the book as held), use `get_strategy_performance_summary` /
`get_strategy_track_record` instead.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`strategy_name`	No	Narrow to one strategy (e.g. "momentum", "multi_signal", "fundamentals_smid", "value_quality"); omit for picks across all strategies.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`picks`	Yes	Current holdings, each strategy at its own latest rebalance.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds genuinely useful context: synchronous execution, no auth required, and the semantic distinction between current-basket YTD returns and realized track record. It stops short of rate limits or response-size behavior, keeping it just below the top tier.

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 core purpose in the first sentence, followed by return semantics and routing guidance in logical order. It is slightly long, but nearly every sentence carries a distinct fact, so there is little waste.

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?

An output schema exists, so return values needn't be enumerated, yet the description still clarifies the semantics of ytd_return and basket_ytd_return. Combined with the no-auth/read-only disclosure and sibling routing, nothing an agent needs to call this correctly is missing.

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 single strategy_name parameter is already documented with examples in the schema; the description text adds no further parameter guidance. Baseline 3 is correct when the schema does the heavy lifting.

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?

States a specific verb and resource ('Fetch the latest LLM-selected stock picks') and immediately clarifies scope with 'current rebalance holdings.' It also names the sibling tools it is not, so an agent can route between this and the performance tools without opening schemas.

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?

Explicitly names the alternatives (get_strategy_performance_summary / get_strategy_track_record) and the condition that selects them ('how the strategies have ACTUALLY performed since inception'), contrasting with the current-basket YTD view this tool provides. Clear when/when-not guidance.

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?