Skip to main content
Glama

SophiaLabs & Nomos Open-Core MCP

inspect_dod_gates

Read-onlyIdempotent

Inspect the 42 compiled Go/AST Definition of Done gates, ERR_* failure diagnostics, and container/symlink/CapBAC IFC sandbox rules.

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

Input Schema

NameRequiredDescriptionDefault
lawNoOptional Canonical Law number (1..7)
gate_idNoOptional gate identifier such as G-01 or G-16
categoryNoOptional category slug: ast, phase, sandbox, security, testing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds useful scope information — the count of 42 gates and the inclusion of ERR_* diagnostics and CapBAC/symlink/container sandbox rules — which tells the agent what content lives behind the call. It does not describe result shape, ordering, or size of the payload.

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?

A single front-loaded sentence with no filler; the resource inventory is stated before any qualifications. It is dense with domain jargon but every clause names actual content categories the tool exposes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should ideally indicate what an inspection returns (per-gate records, diagnostic text, rule tables) and how filtering composes. It gives enough to know the domain but leaves the agent guessing about response structure for a tool with three independent optional filters.

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% and each parameter already carries its own description and examples (G-01, law 1..7, category slugs), so the schema does the heavy lifting. The description only implicitly reinforces the filterable content categories (ERR_* diagnostics, sandbox rules) and adds no syntax or combination semantics beyond the schema.

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 (Inspect) and a concrete resource (the 42 compiled Go/AST Definition of Done gates, ERR_* diagnostics, sandbox rules), so an agent knows it is a catalog/rule lookup rather than an action. It does not distinguish itself from siblings such as search_nomos_corpus or compare_governance_approaches, leaving ambiguity about which lookup to choose.

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?

No when-to-use guidance is offered: nothing says whether to call this before a change, in response to a gate failure, or instead of searching the corpus. The optional law/gate_id/category parameters imply filtered lookup, but the agent must infer all of that from the schema.

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.