Skip to main content
Glama

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

by pl.agentrynku
OverviewDiscussionsAdmin

modify_chat_settings

Ustawienia powiadomień: próg istotności, kanały, wyciszone klasy alertów.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelsNoActive alert channels. SMS not yet supported. Empty array silences alerts entirely.
alertWeightingNoHow the per-ticker daily alert cap treats companies you do NOT hold. 'flat' (default, unchanged behaviour): every ticker gets the same 5/day cap. 'portfolio_first': tickers absent from your holdings get 2/day instead; positions you hold keep 5/day. Measured on a real 90-day account (3875 candidates): 1840 alerts under flat vs 1482 under portfolio_first, with a watchlist-only ticker dropping 186 → 95 and the largest position unchanged at 5 (its cap was never the binding constraint — it had 5 candidates in 90 days). Alias-aware: a position stored as KGH counts as held when the news says KGHM. With an empty holdings list this setting does nothing, so it cannot mute everything.
notificationEmailNoOverride email (null clears, falling back to UserDoc.email).
impactThresholdPctNoMinimum extent of the predicted range from zero in percentage points: max(|rangeLowPct|, |rangeHighPct|) (default 2, ≥ 0). This filters range extent, not the expected directional move.
espiCommunicationsEnabledNoSend every official ESPI/EBI filing for watched companies. These entries are marked as communications, not alerts, and do not enter alert limits or performance history.
mutedAlertClassificationsNoMute-lista klasyfikacji alertów — te typy nie będą wysyłane jako alerty o nowych zdarzeniach. Pusta = nic nie wyciszone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / mutedAlertClassifications / description
      Previous value: -"Mute-lista klasyfikacji alertów — te typy nie będą wysyłane realtime. Pusta = nic nie wyciszone."New value: +"Mute-lista klasyfikacji alertów — te typy nie będą wysyłane jako alerty o nowych zdarzeniach. Pusta = nic nie wyciszone."
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

The annotation readOnlyHint=false indicates a write operation, but the description adds no behavioral context beyond that. It does not state side effects, such as whether changes apply immediately, persist across sessions, override delivery preferences, or affect existing alert subscriptions.

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

Conciseness3/5

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

The description is a single short fragment with no wasted words and is front-loaded with the main topic. However, it is so terse that it reads more like a subtitle than a functional definition, and a complete sentence explaining the action would improve usability without adding bulk.

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 mutating tool with six optional parameters, no output schema, and no usage guidance, the description is incomplete. An agent cannot determine what to expect after calling it, how it interacts with alert delivery, or how fields like notificationEmail and espiCommunicationsEnabled fit into the overall behavior without examining the schema.

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 the schema already documents all parameters thoroughly. The description's phrase 'próg istotności, kanały, wyciszone klasy alertów' loosely maps to impactThresholdPct, channels, and mutedAlertClassifications, but it adds no new meaning beyond the schema.

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?

The description identifies the tool as dealing with notification settings and enumerates three concrete areas: significance threshold, channels, and muted alert classes. The action is implicit ('Ustawienia' rather than 'Zmień'), but the tool name 'modify_chat_settings' makes the intent clear. It does not explicitly distinguish itself from settings-like siblings, but its resource and scope are recognizable.

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 is given on when to use this tool versus alternatives such as set_agent_prefs, get_alerts, or get_alert_delivery_stats. The description provides no conditions, exclusions, or context for choosing this tool over others.

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