Skip to main content
Glama

Nomos - Deterministic Git & AST Governance for AI Coding Agents

Preview nomos.yaml & CI Workflow Templates

scaffold_nomos_config
Read-onlyIdempotent

Preview read-only nomos.yaml configuration text, 4-line GitHub Actions SARIF workflow text, and Day-0 onboarding commands without modifying files. Example: project_name='payments-api', mode='local' returns template text. Use when retrieving ready-to-paste YAML config and CI workflow templates. Do NOT use when requesting a strategic rollout recommendation by LOC or air-gap posture (use recommend_adoption_plan 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": {
      "mode": "local",
      "languages": [
        "go",
        "typescript"
      ],
      "project_name": "payments-api"
    },
    "name": "scaffold_nomos_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoOnboarding mode: branch (default), local (stealth .git/info/exclude), or worktrees.branch
languagesNoTarget languages in the repository.
ci_providerNoCI platform for verification workflow output (defaults to github).github
project_nameNoRepository or project slug.my-service

Output Schema

NameRequiredDescriptionDefault
modeYesSelected isolation mode.
projectYesSanitized project slug.
summaryYesDeterministic Markdown configuration bundle.
nomosYamlYesGenerated nomos.yaml template.
ciProviderYesSelected CI provider.
canonicalUrlYesCanonical quickstart URL.
ciWorkflowYamlYesGenerated CI pipeline YAML.
dayZeroCommandsYesDay-0 CLI bootstrap commands.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/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 the safety profile is covered. The description adds genuine context beyond that by naming the concrete payloads returned (template config text, workflow snippet, Day-0 commands) and reinforcing that no files are written. It stops short of noting that output is fixed template text with no project-specific derivation, which is the only remaining ambiguity.

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 output inventory, then usage, then exclusion — a sound ordering with no filler. The inline example is somewhat redundant given a fully described schema and an output schema, which keeps it off a 5.

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?

For a zero-required-parameter, read-only preview tool with an output schema, the definition covers what is produced, when to call it, and which sibling to prefer instead. No behavior an agent needs in order to invoke it correctly is missing.

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 the mode enum is already documented in the schema, including the stealth .git/info/exclude meaning, so the baseline is 3. The worked example (project_name='payments-api', mode='local') shows how parameters combine, but adds no semantics the schema does not already carry.

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 names a specific verb (Preview) and enumerates the exact artifacts produced: nomos.yaml configuration text, a 4-line GitHub Actions SARIF workflow, and Day-0 onboarding commands. It also states the non-mutating scope, so an agent can separate it from recommend_adoption_plan without inspecting schemas.

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 gives an explicit positive trigger ('Use when retrieving ready-to-paste YAML config and CI workflow templates') and an explicit exclusion with the named alternative ('Do NOT use when requesting a strategic rollout recommendation by LOC or air-gap posture (use recommend_adoption_plan instead)'). Nothing about routing is left to inference.

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.