Skip to main content
Glama

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

by pl.agentrynku
OverviewDiscussionsAdmin

list_feature_requests

Read-only

Lista zgłoszeń i ich stan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoOrdering. 'priority' (default) = queue order: P0 first, oldest first within a rank, unranked treated as P2. 'newest' = createdAt desc (what this tool did before). 'oldest' = createdAt asc.
briefNoHeadline mode: id, type, status, title, priority, createdAt, updatedAt, truncated founderNote, autoImplAttempts. Omits description and autoImplLastError.
limitNoDefault 20, max 50.
ownerNoOptional filter by owner handle. 'operator' finds what needs a human decision, 'unassigned' finds requests nobody owns.
offsetNoSkip this many rows IN THE SELECTED ORDER before returning the page. Default 0. With the default sort:'priority' that means skipping queue-ordered rows (so a large offset skips urgent work, not old history) - pass sort:'newest' when you want to page back through history. Combine with total/hasMore to walk the whole list.
statusNoOptional filter.
priorityNoOptional filter by declared priority. Matches legacy spellings of the same rank too (P1 also finds 1 and 'high'). Requests nobody ranked are NOT returned by any value - absent priority is a separate state.
reporterNoOptional filter by reporter handle. Pass your own session name to see everything YOU filed, whoever ended up owning it. 'unassigned' finds requests filed before reporters were recorded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true, so the safety profile is already known. The description adds no behavioral context, such as default sorting, pagination behavior, or any caveats. It neither contradicts nor enriches the annotation.

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 short sentence, which is concise but under-specified for a tool with 8 parameters and no output schema. It does not front-load important usage context and is not appropriately sized for the tool's complexity.

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?

For a tool with 8 parameters, rich schema descriptions, and no output schema, the description lacks an overview of the tool's purpose, typical use cases, or return behavior. The schema covers parameters, but the description leaves the agent without a high-level understanding.

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 parameter descriptions are detailed (e.g., explaining sort order and offset semantics). The description itself adds no parameter meaning beyond what the schema provides, so the baseline of 3 applies.

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

Purpose2/5

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

The description 'Lista zgłoszeń i ich stan.' (list of reports and their status) states a verb and resource but is vague. It does not clarify what kind of requests, the domain context, or how it differs from sibling list tools like get_alerts or list_webhook_events. It is not a tautology but lacks specificity.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. It does not mention any conditions, exclusions, or alternative tools. An agent gets no help deciding between this and other listing tools.

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