Skip to main content
Glama

Get one rule edit

get_rule_change
Read-onlyIdempotent

One recorded rule edit by its id: the full text before and after on each changed field, the removed and added words, when it was recorded, the Yes price before, at and after, the other markets the same edit landed on, and the market's other edits. Ids come from a list of recent edits, a market's edit history, or a RulesWatch change link (/change/).

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": {
      "id": "<id>"
    },
    "name": "get_rule_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe edit's id, the number in its RulesWatch link.

Output Schema

NameRequiredDescriptionDefault
idNo
urlNo
kindNo
foundNo
venueNo
fieldsNo
marketNo
messageNo
summaryNo
market_idNo
kind_labelNo
market_urlNo
recorded_atNo
market_titleNo
market_historyNo
yes_price_afterNo
yes_price_beforeNo
yes_price_at_editNo
other_markets_same_editNo
same_edit_on_other_marketsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so safety is covered. The description adds real behavioral context beyond that: the record includes before/after text per changed field, word-level diffs, timestamps, pre/at/post Yes prices, and the other markets the same edit propagated to — details that shape whether this call answers the user's question.

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?

Front-loaded with the core purpose, but the long comma-chained enumeration of returned fields is heavy and partly duplicates what the output schema already declares. It reads as one run-on sentence where a shorter purpose statement plus sourcing line would serve better.

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

Completeness4/5

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

With an output schema, full annotation coverage, and a single well-documented required parameter, the agent has nearly everything needed. The only gap is no note on behavior for an unknown or deleted id, which matters for a lookup-by-key tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the property already explains that id is the number in the RulesWatch link, so the baseline is 3. The description goes further by naming three concrete sources of ids, adding retrieval meaning the schema does not carry.

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?

States a specific verb+resource ('One recorded rule edit by its id') and enumerates what the record contains, which makes it clearly distinct from the plural sibling recent_rule_changes. An agent can identify this as the single-item detail lookup without opening any schema.

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?

Explicitly tells the agent where valid ids come from — a recent-edits list, a market's edit history, or a RulesWatch /change/<id> link — which is actionable routing guidance. It stops short of an explicit exclusion ('do not use to browse edits'), but the sourcing note implies the right upstream tools.

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.