Skip to main content
Glama

Recent rule changes

recent_rule_changes
Read-onlyIdempotent

The newest recorded edits to Polymarket and Kalshi market rules, newest first, each with the removed and added words, the Yes price at the edit and a link. Filter by venue, kind of edit, category or title words. Use it for questions like "what rules changed this week" or "any new Kalshi clarifications".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recent_rule_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOnly this kind of edit: clarification (text added to settle a case), rules (rules text edited), source (resolution source changed), dispute (Polymarket outcome disputed), dates (end date moved), title (title changed). Leave out for all of them.
limitNoHow many edits to return. Default 10.
queryNoOnly edits on markets whose title holds these words, as a phrase.
venueNoOnly edits on this venue: pm (or polymarket) or kalshi.
categoryNoOnly markets in this category.
before_idNoFor the next page: the next_before_id from the previous answer.

Output Schema

NameRequiredDescriptionDefault
moreNo
noteNo
changesNo
filtersNo
next_before_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / before_id
      Added value: +{
      +  "description": "For the next page: the next_before_id from the previous answer.",
      +  "maximum": 999999999999,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "Only markets in this category.",
      +  "enum": [
      +    "politics",
      +    "sports",
      +    "crypto",
      +    "economy",
      +    "weather",
      +    "world",
      +    "culture",
      +    "tech",
      +    "other"
      +  ],
      +  "maxLength": 20,
      +  "type": "string"
      +}
    • addedInput schema / properties / kind
      Added value: +{
      +  "description": "Only this kind of edit: clarification (text added to settle a case), rules (rules text edited), source (resolution source changed), dispute (Polymarket outcome disputed), dates (end date moved), title (title changed). Leave out for all of them.",
      +  "enum": [
      +    "clarification",
      +    "rules",
      +    "source",
      +    "dispute",
      +    "dates",
      +    "title"
      +  ],
      +  "maxLength": 20,
      +  "type": "string"
      +}
    • addedInput schema / properties / limit / description
      Added value: +"How many edits to return. Default 10."
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "Only edits on markets whose title holds these words, as a phrase.",
      +  "maxLength": 80,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • addedInput schema / properties / venue
      Added value: +{
      +  "description": "Only edits on this venue: pm (or polymarket) or kalshi.",
      +  "enum": [
      +    "pm",
      +    "polymarket",
      +    "kalshi"
      +  ],
      +  "maxLength": 10,
      +  "type": "string"
      +}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "changes": {
      +      "items": {
      +        "properties": {
      +          "fields": {
      +            "items": {
      +              "properties": {
      +                "added": {
      +                  "type": [
      +                    "string",
      +                    "null"
      +                  ]
      +                },
      +                "after": {
      +                  "type": [
      +                    "string",
      +                    "array"
      +                  ]
      +                },
      +                "before": {
      +                  "type": [
      +                    "string",
      +                    "array"
      +                  ]
      +                },
      +                "field": {
      +                  "type": [
      +                    "string",
      +                    "null"
      +                  ]
      +                },
      +                "removed": {
      +                  "type": [
      +                    "string",
      +                    "null"
      +                  ]
      +                },
      +                "truncated": {
      +                  "type": "boolean"
      +                }
      +              },
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "id": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "kind": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "kind_label": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "market_id": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "market_title": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "market_url": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "recorded_at": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "same_edit_on_other_markets": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "summary": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "url": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "venue": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "yes_price_at_edit": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "yes_price_before": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "filters": {
      +      "items": {
      +        "type": [
      +          "string"
      +        ]
      +      },
      +      "type": "array"
      +    },
      +    "more": {
      +      "type": "boolean"
      +    },
      +    "next_before_id": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "note": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds behavior beyond that: newest-first ordering, the exact payload fields (removed and added words, Yes price at the edit, link), and filter scoping. It says nothing about result caps or pagination depth, though limit and before_id are documented in the schema.

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?

Three sentences, front-loaded with the resource and ordering, then filter axes, then usage examples. Every sentence carries information an agent needs, and there is no filler.

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?

Six optional parameters with full schema coverage and an output schema covering return shape, so the description does not need to explain further. It still names the key returned fields and the newest-first ordering, which is enough for an agent to call it correctly against a read-only, idempotent tool.

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 enum meanings for kind and venue and the before_id pagination hint, so the baseline is 3. The description only restates the filter axes ('venue, kind of edit, category or title words') without adding new parameter meaning. It neither strengthens nor weakens what the schema already documents.

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 gives a specific verb and resource: it returns the newest recorded edits to Polymarket and Kalshi market rules, ordered newest first, with removed/added words, the Yes price at edit time and a link. That is far more than a restatement of the name. It never explicitly contrasts itself with the singular sibling get_rule_change, so sibling differentiation is only implied by 'newest' and plural scope.

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?

It supplies concrete when-to-use framing with two example questions ('what rules changed this week', 'any new Kalshi clarifications') and notes the available filter axes. There are no explicit exclusions or a named alternative for looking up a single edit, which keeps it short of a 5.

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.