Skip to main content
Glama

List source-linked rule review work

list_rule_review_queue
Read-onlyIdempotent

Returns implemented rule claims and their passage, rule, reviewer, contradiction, and publication state. Each item also lists draftSources: the book lines the code draws the rule from, marked not reviewed. Draft sources are never citations of reviewed doctrine.

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_rule_review_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
moduleNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
summaryYes
publicationRuleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / default
      Previous value: -50New value: +100
    • changedInput schema / properties / module / enum
      Previous value: -[
      -  "muhurta",
      -  "dosha",
      -  "interpretation",
      -  "kp",
      -  "jaimini",
      -  "varshaphal"
      -]New value: +[
      +  "muhurta",
      +  "dosha",
      +  "interpretation",
      +  "judgment",
      +  "natal-panchanga",
      +  "kp",
      +  "jaimini",
      +  "varshaphal"
      +]
  2. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful semantics — that draftSources are marked not reviewed and are never citations of reviewed doctrine — but says nothing about ordering, the hard 100-item cap, or how results are paged, which matters for a queue-listing tool.

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 short sentences, front-loaded with the payload description, and no filler. The final sentence is a slight restatement of 'marked not reviewed' but earns its place as an explicit anti-misuse warning.

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 explaining return shape is largely redundant but harmless, and the draftSources caveat is a real addition. The gaps are the undocumented 'module' filter and the unstated 100-item cap, which an agent calling a review-queue tool would reasonably want before invoking it.

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

Parameters2/5

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

Schema description coverage is 0% and the description never mentions either parameter. The 8-value 'module' enum is completely unexplained — no indication of what a module scopes or how it filters — and the 'limit' cap/default of 100 is undocumented in prose. The description does not compensate for the coverage gap.

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?

States a specific verb+resource: returns implemented rule claims with passage, rule, reviewer, contradiction, and publication state, plus draftSources. This is concrete enough to distinguish it from analysis tools, but it never names the close siblings (search_reviewed_rules, get_rule_citations, get_book_rule_findings), so the boundary is left implicit.

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

Usage Guidelines2/5

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

There is no statement of when to call this versus search_reviewed_rules or get_rule_citations, and no prerequisites (e.g., that this surfaces unreviewed work rather than reviewed doctrine). The closing note about draft sources is a data caveat, not usage routing, so the agent must infer the selection condition.

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.

Resources