Skip to main content
Glama

list_unreviewed_rulings

List curated rulings that still need human review, ordered by authority, judge tier, and date. Use it to find pending items and track curation progress.

Instructions

List curated rulings pending human review (reviewed=False), ordered by authority, judge_tier (tier_0 > tier_2 > tier_1), and date DESC (default limit=20, max 100).

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": "list_unreviewed_rulings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

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 disclosure burden and does a fair job: it declares the exact sort order (authority, then judge_tier with the non-obvious tier_0 > tier_2 > tier_1 precedence, then date DESC) and the result-size bounds. It omits any statement about read-only safety, permissions, or pagination past the limit cap, so it is not fully complete.

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?

A single sentence with no waste, front-loading the filter and then the ordering, and ending with the limit bounds. Nothing redundant relative to the structured fields.

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 shape needn't be explained, and the filter, ordering, and size limits are all covered for a one-parameter read tool. The only real gap is the absence of any permission or read-only disclosure, which matters more given zero annotations.

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 only parameter is limit, which the schema documents merely as an integer with default 20. The description adds the ceiling ('max 100') that the schema does not state, which is genuinely useful for planning calls.

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 ('List') and a precisely scoped resource ('curated rulings pending human review (reviewed=False)'). The reviewed=False qualifier does the work of distinguishing it from sibling listing tools like export_rulings or get_card_rulings without needing to name them.

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?

The 'pending human review' framing implies the use case (working the review queue), and mark_ruling is the obvious follow-up by name. But the description never states when to use this versus export_rulings or search, and offers no exclusions or prerequisites, leaving routing to inference.

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