Skip to main content
Glama

Inspect Compiled DoD Gates, Hooks & Directives

nomos_capabilities
Read-onlyIdempotent

Inspect compiled quality gates, Git hooks, phase directives, or remediation guidance for a gate ID. Use to look up invariants, hook behavior, or fixes; not for project history or source scans.

Instructions

Inspect compiled Nomos Definition of Done quality gates, ambient Git/session hooks, embedded phase directives, or remediation guidance for a specific gate ID. Use when looking up gate invariants, hook behavior, or how to fix a specific gate ID. Do NOT use when searching project-specific historical decisions in Mneme (use nomos_mem_recall instead) or scanning live source files (use nomos_xray instead).

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

Input Schema

NameRequiredDescriptionDefault
idNoOptional capability, gate, or directive identifier to inspect in detail.
typeNoOptional capability category filter.

Output Schema

NameRequiredDescriptionDefault
gates_countNoTotal active quality gates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that content is "compiled" rather than live source, which explains why it differs from nomos_xray, but it says nothing about how results are returned or whether an unknown ID errors or returns empty.

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 sentences, front-loaded with the resource list, then the positive usage case, then the exclusions. No filler, though the positive-use sentence partially repeats the resource list from the opening sentence.

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 no explanation, and the routing guidance is complete for a two-parameter read-only lookup. The only real gap is that the "engine" and "cli" capability types available in the enum go unmentioned in prose.

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 description coverage is 100%, so both parameters are already documented, and the description only restates that `id` targets a specific gate and implies category filtering. Notably the enum includes "engine" and "cli" categories that the description never mentions, so it does not extend parameter meaning beyond the schema.

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 ("Inspect") applied to concrete resources: compiled Definition of Done quality gates, ambient Git/session hooks, embedded phase directives, and remediation guidance. An agent can distinguish this registry-inspection tool from sibling lookup tools without opening the schema.

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?

Explicitly gives both sides: use when looking up gate invariants, hook behavior, or remediation for a gate ID; do NOT use when searching project-specific historical decisions (route to nomos_mem_recall) or scanning live source files (route to nomos_xray). Both alternatives are named with the condition that selects them.

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