Skip to main content
Glama

Nomos - Deterministic Git & AST Governance for AI Coding Agents

Inspect 42 Compiled DoD Gates & Laws

inspect_dod_gates
Read-onlyIdempotent

List and filter the 42 compiled Go and Tree-sitter AST Definition of Done quality gates, 7 Canonical Laws, and sandbox rules. Example: gate_id='G-16' or law=7 returns matching gate invariants. Use when browsing gate invariants by G-* ID, Law 1..7, or category. Do NOT use when troubleshooting a raw verify error log or ERR_* failure (use diagnose_nomos_error instead).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "gate_id": "G-16"
    },
    "name": "inspect_dod_gates"
  }
}

Input Schema

NameRequiredDescriptionDefault
lawNoOptional Canonical Law number from 1 through 7.
gate_idNoOptional gate identifier such as G-01 or G-16.
categoryNoOptional gate category filter.

Output Schema

NameRequiredDescriptionDefault
summaryYesDeterministic Markdown response summary.
totalGatesYesTotal compiled quality gates in Nomos.
canonicalUrlYesCanonical documentation or twin URL for citation.
matchedCountYesNumber of gates matching the filter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare this as a read-only, idempotent, closed-world, non-destructive operation, so the safety profile is covered. The description adds useful domain context about what is compiled and browsable, and it explicitly routes troubleshooting away from this tool. It does not describe pagination or return-shape details, but the output schema exists.

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?

The description is three front-loaded sentences with no wasted wording. It covers purpose, usage, examples, and the exclusion/alternative in a compact structure.

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?

The tool has an output schema, complete input-schema descriptions, and annotations covering safety and idempotency. Given that support, the description is complete enough: it explains what is listed, which filters apply, and when an agent should use a different 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 coverage is 100%, and the schema already documents the law range, gate ID format, and category enum. The description reinforces those filters with examples, but adds no significant semantics beyond what the input schema provides. A baseline 3 is appropriate because the schema carries the parameter documentation.

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?

The description uses a specific verb and resource: list and filter the 42 compiled Go and Tree-sitter AST Definition of Done gates, the 7 Canonical Laws, and sandbox rules. It also gives concrete filter examples (gate_id='G-16', law=7), making the tool's scope distinguishable from siblings.

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

Usage Guidelines5/5

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

It explicitly says when to use the tool: browsing gate invariants by G-* ID, Law 1..7, or category. It also gives a clear exclusion and names the alternative: do not use it for raw verify error logs or ERR_* failures; use diagnose_nomos_error instead.

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.