Skip to main content
Glama

Nomos - Deterministic Git & AST Governance for AI Coding Agents

Search Nomos Docs, Dispatches & Specs

search_nomos_corpus
Read-onlyIdempotent

Search Nomos Engineering Handbook chapters, Empirical Field Dispatches, Open-Core Architecture Specs, and CLI reference by keyword. Example: query='worktree isolation', section='handbook' finds chapters on Git worktrees. Use when looking up conceptual architecture, empirical benchmarks, or CLI flags. Do NOT use when inspecting a specific G-* gate or ERR_* code (use inspect_dod_gates or diagnose_nomos_error instead) or comparing external tools (use compare_governance_approaches 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": {
      "query": "worktree isolation",
      "section": "handbook"
    },
    "name": "search_nomos_corpus"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesKeywords or engineering problem phrase to search across the public Nomos corpus.
sectionNoCorpus subset filter (defaults to all).all

Output Schema

NameRequiredDescriptionDefault
queryYesNormalized search query.
summaryYesDeterministic Markdown response summary.
matchCountYesNumber of top corpus matches returned.
canonicalUrlYesCanonical documentation or twin URL for citation.

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 establish that this is a read-only, idempotent, non-destructive, non-open-world operation. The description adds useful scope about searching the public Nomos corpus by keyword and via section filters, though it does not describe ranking, result limits, or pagination behavior.

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 front-loaded with the core action and corpus scope, followed by an example, use cases, and exclusions. Every sentence contributes to selection or invocation guidance without unnecessary repetition.

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?

Given a simple two-parameter search tool with full schema coverage, rich read-only annotations, and an output schema, the description provides enough context to use it correctly. It covers purpose, examples, when to use, and when to choose alternatives.

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 the schema already defines both parameters and the section enum. The description includes a concrete example linking query and section to a result type, which adds some meaning, but it does not provide additional syntax or semantic detail 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?

The description gives a specific verb, "Search," and enumerates the exact corpus resources covered: Handbook chapters, Field Dispatches, Architecture Specs, and CLI reference. It also provides an example query and makes clear how this differs from sibling tools such as inspect_dod_gates and diagnose_nomos_error.

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 states when to use the tool (conceptual architecture, empirical benchmarks, CLI flags) and includes clear exclusions with named alternatives for gate inspection, error diagnosis, and external tool comparison. The guidance is specific enough for an agent to choose this tool without opening 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.