Skip to main content
Glama

mark_ruling

Update a ruling’s reviewed status, judge tier, or superseded-by link so outdated guidance stays traceable without deletion.

Instructions

Update a ruling's reviewed status, link it as superseded_by a newer ruling_id, and/or set judge_tier ('tier_0' | 'tier_2' | 'tier_1' for source='judge'). Never deletes outdated rulings; rejects self-superseding and circular chains.

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": {
      "ruling_id": "<ruling_id>"
    },
    "name": "mark_ruling"
  }
}

Input Schema

NameRequiredDescriptionDefault
reviewedNo
ruling_idYes
judge_tierNo
superseded_byNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that outdated rulings are never deleted, and that self-superseding and circular chains are rejected — validation behavior an agent could not infer otherwise. It stops short of saying whether null fields mean 'leave unchanged', which matters for a partial-update tool.

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?

Two dense sentences that front-load the mutating actions, then the guardrails. No filler and no repetition of the tool name as content.

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?

An output schema exists, so return values need not be described, and the guardrail behavior is covered. The remaining gap is the null/omission semantics for the three optional parameters on a partial-update operation.

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 0% and the schema declares judge_tier as an untyped string with no enum, so the description's enumeration ('tier_0' | 'tier_2' | 'tier_1') is a real value-add, as is the note that superseded_by must reference a newer ruling_id. The 'reviewed' parameter's tri-state null semantics remain unexplained.

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 (update/mark) on a specific resource (a ruling) and enumerates exactly the three mutations it performs: reviewed status, superseded_by link, and judge_tier. The 'and/or' framing makes clear these are independently selectable, distinguishing it from add_ruling without needing the sibling's schema.

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

Usage Guidelines3/5

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

Implies usage through option description ('and/or') and one conditional rule ('judge_tier' applies only for source='judge'), which is genuinely useful. However, it never states when to prefer this over add_ruling or how it relates to list_unreviewed_rulings, and gives no explicit when-not-to-use guidance.

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