Flexreport Finance

screen_stocks

Screen stocks by financial growth, sector, sub-industry, market cap, analyst ratings, institutional ownership, country, and price performance.

Discover valid filter values with the list tools named in each parameter's
description before guessing.

Rate-limited to 10/hour
per user server-side.

Asynchronous: returns a task id. Poll it with `get_task_status` until SUCCESS.

Input Schema

TableJSON Schema

Name	Required	Description
`metrics`	No	Financial-growth criteria: metric name -> threshold (number) or required flag (bool), e.g. {"revenue_growth": 0.1, "positive_eps": true}. Interpreted by the screener, not enum-validated.
`sectors`	No	Sector values from list_options("sectors").
`countries`	No	Country values from list_options("countries").
`market_cap`	No	Market-cap buckets from list_options("market_cap"), e.g. "Small-cap", "Large-cap".
`sub_sectors`	No	Sub-industry values from list_sub_industries([...]).
`analyst_ratings`	No	Analyst consensus ratings to keep, e.g. ["Buy", "Strong Buy"].
`price_performance`	No	Price-return criteria: window -> minimum return, e.g. {"ytd": 0.1}.
`institutional_ownership`	No	Investor category -> minimum ownership, keyed by list_options("institutional_investor_types") values, e.g. {"Hedge Fund": 5}.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes	PENDING on submission.
`task_id`	Yes	Poll with get_task_status until SUCCESS.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds two traits the annotations do not convey: a server-side rate limit of 10/hour per user and asynchronous execution returning a task id that must be polled. These are exactly the operational facts an agent needs to avoid retry storms and to correctly sequence calls.

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?

Four short blocks: what it filters, how to obtain valid values, the rate limit, and the async contract. The purpose is front-loaded and every line carries distinct operational value with no filler.

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?

Covers prerequisites, rate limiting, and the async/polling lifecycle, and an output schema exists so return-shape explanation is unnecessary. For an eight-parameter screener, nothing an agent needs to invoke it 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 each parameter already names its source list tool, so the description's opening enumeration mostly restates the schema. It adds no threshold syntax or value-format guidance beyond what the schema provides, making the baseline 3 appropriate.

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 (screen) and resource (stocks) and enumerates the eight filter dimensions it accepts, which cleanly separates it from adjacent tools like get_stock_picks or generate_report_for_stock. An agent can tell what this tool does without opening the schema.

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?

Gives a concrete prerequisite workflow: discover valid filter values via the list tools named in each parameter description before guessing, and poll the returned task with get_task_status until SUCCESS. It lacks any explicit when-not or comparison against sibling screening/picks tools, so it stops short of a 5.

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?