Skip to main content
Glama

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

by pl.agentrynku
OverviewDiscussionsAdmin

get_news_history

Read-only

Historia depesz o spółce razem z ich oceną.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results. Default 20, max 100.
symbolYesRequired. Server canonicalizes.
sourcesNoOptional allowlist of source values. Applied before limit; e.g. ['gpw-espi', 'gpw-espi-archive', 'pap:biznes'] returns ESPI and PAP without forum rows. Omit to preserve the default of all sources.
sinceIsoNoISO date. Default 30 days ago.
universeNoOpcjonalny rynek symbolu. Ten sam ticker może należeć do spółek na obu rynkach, więc podaj universe, aby wskazać właściwy instrument; bez niego jednoznaczny symbol rozstrzyga kolekcja assets, a homograf domyślnie wybiera polish-stocks. Odpowiedź zawsze zwraca universeUsed, a przy domyślnym wyborze homografu także universeNote.
classificationNoOptional: earnings | preliminary_results | earnings_conference | regulatory | ma | guidance | operational | sentiment | macro | management | other.
includeOtherSubjectsNoDefault false. When true, also returns evaluations written about OTHER companies that merely tag this ticker (pre-2026-08-18 behaviour). Use only when you want the full article context, not this company's own newsflow.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

readOnlyHint=true already covers the safety profile, and the description adds that evaluations are returned alongside news. It does not describe ordering, pagination, or what the 'assessment' actually represents, but there is no contradiction 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?

The description is a single, front-loaded sentence with no redundant wording. Every word contributes to identifying the tool's purpose.

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

Completeness3/5

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

With seven parameters and no output schema, the one-line description leaves the meaning of returned evaluations and selection context under-specified. The detailed schema covers invocation mechanics, but not the absent output/behavior richness.

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 all seven parameters are documented in the schema. The description adds no parameter-specific meaning beyond what the schema already provides, which warrants the baseline score.

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

Purpose4/5

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

Description states a specific resource (company dispatch/news history) and the added value (evaluations/assessments), making the tool's purpose clear. It does not explicitly differentiate from sibling get_* tools, so it misses the top score.

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 when-to-use guidance, prerequisites, or alternatives are described. The agent must infer when to choose this over similar tools like get_company_analysis or get_activity_feed.

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