Skip to main content
Glama

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

modify_watchlist

Dodanie lub usunięcie spółki z watchlisty.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addNoSymbols to add (uppercased server-side).
removeNoSymbols to remove.
setAlarmNoSet, re-arm, or clear one-shot price alarms. Example: `setAlarm: [{symbol: 'KGHM', price: 130, direction: 'below'}]`.
universeNoAsset universe. Default: 'polish-stocks'. ROZSTRZYGA HOMOGRAF: ten sam kod bywa dwiema spółkami (CRM to Cormay na GPW i Salesforce w USA), a wpis watchlisty jest parą (rynek, symbol). Bez tego pola operacja na kodzie, który użytkownik trzyma na OBU rynkach, nie zgaduje strony - wraca w polu `niejednoznaczne` z prośbą o rynek i nie zmienia niczego.
setThresholdNoSet per-asset notification threshold for one or more symbols already in the watchlist. Symbols not yet on the watchlist are auto-added.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / setAlertsActive
      Removed value: -{
      -  "description": "Free plan: choose which watchlist symbols get news alerts (at most 5 active). Enabling a sixth is refused and comes back in `alertsRejectedByLimit`; disable another first. On PRO every symbol has alerts and this is a no-op (`alertsAlwaysOn`).",
      -  "items": {
      -    "properties": {
      -      "active": {
      -        "description": "true = send news alerts for this watchlist symbol, false = keep it on the list without alerts.",
      -        "type": "boolean"
      -      },
      -      "symbol": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "symbol",
      -      "active"
      -    ],
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
  2. Changed1 schema field changed
    • addedInput schema / properties / setAlertsActive
      Added value: +{
      +  "description": "Free plan: choose which watchlist symbols get news alerts (at most 5 active). Enabling a sixth is refused and comes back in `alertsRejectedByLimit`; disable another first. On PRO every symbol has alerts and this is a no-op (`alertsAlwaysOn`).",
      +  "items": {
      +    "properties": {
      +      "active": {
      +        "description": "true = send news alerts for this watchlist symbol, false = keep it on the list without alerts.",
      +        "type": "boolean"
      +      },
      +      "symbol": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "symbol",
      +      "active"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  3. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations indicate readOnlyHint=false, confirming mutability, but the description adds no behavioral details beyond the basic add/remove action. It doesn't mention side effects like auto-adding symbols when setting thresholds or the ambiguity handling described in the universe parameter, leaving agents without key behavioral context.

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 extremely concise (one short sentence) and front-loaded, which is good for readability. However, it sacrifices completeness, omitting the alarm and threshold features, so the conciseness does not earn its place given the tool's complexity.

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

Completeness1/5

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

With 5 parameters covering add/remove, alarms, thresholds, and universe selection, a one-sentence description is grossly inadequate. It fails to mention alarms and thresholds entirely, and provides no information about the universe parameter's role in disambiguating homoglyphs, leaving agents without essential context for correct invocation.

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% and every parameter has a description, so the baseline is 3. The description itself adds no parameter-level meaning; it simply restates 'adding or removing a company' without referencing the alarm, threshold, or universe parameters.

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 states a clear verb (add/remove) and resource (watchlist), which makes the core purpose understandable. However, it omits the alarm and threshold functionality exposed by the schema, so the purpose is partially clear and understates the tool's actual scope.

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?

No guidance is provided on when to use this tool vs. alternatives like modify_holdings, nor are there any conditions or prerequisites for using setAlarm vs. setThreshold. The description gives no contextual clues about appropriate usage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.