Skip to main content
Glama

Link to watch a market for rule changes

get_watch_link
Read-onlyIdempotent

Use when the user wants to be told, alerted or notified when a Polymarket or Kalshi market's rules, resolution source, end date or title change, or wants to watch, follow or track a market for rule edits. Returns a RulesWatch link that opens with that market ready to watch, what an alert covers, and the plan limits. It does not create a watch or change anything: the user opens the link and presses Watch. Needs the market's venue and id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "venue": "<venue>",
      "id": "<id>"
    },
    "name": "get_watch_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe market id. Polymarket: the number in the market's id, like 562802. Kalshi: the market ticker, like KXFEDDECISION-26DEC-H25. A Polymarket or Kalshi link is not an id; search with the link instead.
venueYespm (or polymarket) for Polymarket, kalshi for Kalshi.

Output Schema

NameRequiredDescriptionDefault
idNo
foundNo
plansNo
venueNo
marketNo
messageNo
watch_urlNo
closed_noteNo
suggestionsNo
alert_coversNo
what_happensNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description still adds real context: nothing is persisted, the user must open the link and press Watch, and the link surfaces what an alert covers plus plan limits. That is exactly the kind of side-effect and downstream-workflow disclosure annotations cannot carry.

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

Conciseness4/5

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

Three sentences, front-loaded with the 'Use when' trigger and followed by return behavior and the non-mutating clarification. The synonym chains ('told, alerted or notified'; 'watch, follow or track') are slightly padded but serve intent matching.

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

Completeness5/5

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

With only two required parameters, full schema coverage, annotations and an output schema, nothing essential is missing. The description covers the trigger, the non-mutating nature, and the follow-up step the user must take, which is the main risk of misinvocation here.

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%, including the venue enum and the note that a market URL is not a valid id. The description only restates the requirement ('Needs the market's venue and id') without adding format or edge-case meaning, so the baseline 3 applies.

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

Purpose5/5

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

The description states a specific action (returning a RulesWatch link) tied to a specific resource (a market watched for rule/resolution/end-date/title changes) and enumerates exactly what the alert covers. It also explicitly marks the boundary of the operation ('does not create a watch'), so an agent can tell it apart from market-lookup siblings.

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

Usage Guidelines4/5

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

The trigger is spelled out in user-intent terms ('wants to be told, alerted or notified... or wants to watch, follow or track') plus the concrete change types that qualify. It does not name an alternative sibling such as recent_rule_changes for viewing past changes, so routing between tools is left partly to inference.

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.