Skip to main content
Glama

Agent Rynku - Warsaw Stock Exchange (GPW) data for your agent

by pl.agentrynku
OverviewDiscussionsAdmin

find_opportunities

Read-only

Wyszukiwanie okazji według zadanych kryteriów.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results. Default 10, max 50.
sectorFilterNoOptional sector whitelist (e.g. ['Banki','Energetyka']). Empty = all sectors.
excludeSymbolsNoSymbols to exclude (e.g. user's current portfolio when looking for new ideas). Server canonicalizes.
minSentimentAvg30dNoMinimum sentimentAvg30d (-5..+5). Default unset (no sentiment gate). Use to bias towards momentum (e.g. 1).
minImpliedUpsidePctNoPRO only: minimum forecast.impliedUpsidePct (vs spot) to include. Default 5; ignored for FREE when FREE/PRO is enabled.
forecastFreshnessDaysNoMax age of the FUNDAMENTAL baseline (asset_forecasts.baseline.asOf) in days. Default 400, max 800. Baselines refresh on ANNUAL reports, so a 60-day window returned an empty list for most of the year (FR 0aa64bc4). Each result carries baselineAsOf + baselineAgeDays so you can tell the user how old the fundamentals are.
maxPriceSessionsMissedNoDrop symbols whose last daily candle is older than N CLOSED sessions (weekends/holidays don't count). Default 3 — guards against upside computed against a zombie quote from a delisted or suspended ticker.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / minImpliedUpsidePct / description
      Previous value: -"Minimum forecast.impliedUpsidePct (vs spot) to include. Default 5 — typically a meaningful target threshold."New value: +"PRO only: minimum forecast.impliedUpsidePct (vs spot) to include. Default 5; ignored for FREE when FREE/PRO is enabled."
  2. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, which covers safety. The description adds no behavioral context beyond that—no mention of result format, ordering, or side effects. Parameter descriptions in the schema provide some nuance, but the tool-level description offers nothing new.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, brief sentence, but it is under-specified. Conciseness should pair with substance; here it's shorter than needed to be helpful. It doesn't front-load any critical distinguishing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 optional parameters carrying nuanced behaviors (e.g., forecastFreshnessDays, maxPriceSessionsMissed), no output schema, and many sibling tools, the description is inadequate. The agent lacks context on what this tool returns, how it fits with alternatives, and what edge cases matter.

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 coverage is 100%, so every parameter has a description. The tool description itself adds no parameter information beyond what the schema provides. Baseline of 3 is appropriate since the schema handles documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb ('search') and a resource ('opportunities'), but it's vague about what kind of opportunities. It doesn't distinguish from siblings like find_dip_candidates or find_overheat_candidates. The phrase 'according to given criteria' hints at filtering but doesn't specify the domain or differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. There is no mention of exclusions, preferred contexts, or trade-offs. With many opportunity-related sibling tools, this is a significant gap that leaves the agent to guess which one fits.

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

All Agent Rynku - Warsaw Stock Exchange (GPW) data for your agent toolsInspect
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