Skip to main content
Glama

Nomos - Deterministic Git & AST Governance for AI Coding Agents

Retrieve Progressive Repository Adoption Plan

recommend_adoption_plan
Read-onlyIdempotent

Retrieve a read-only 4-step Nomos rollout guide (X-Ray baseline, stealth Branch Guard, CI SARIF, and isolated Git worktrees) tailored to repository LOC, languages, and air-gap constraints. Example: languages=['go','typescript'], repo_loc=120000 returns a phased brownfield guide. Use when planning rollout steps for a team or monorepo. Do NOT use when previewing raw nomos.yaml and CI workflow templates (use scaffold_nomos_config 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": {
      "repo_loc": 120000,
      "languages": [
        "go",
        "typescript"
      ],
      "ci_provider": "github"
    },
    "name": "recommend_adoption_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
repo_locNoApproximate repository lines of code.
airgappedNoSet true for zero-egress air-gapped local GPU environments.
languagesNoPrimary programming languages in the repository.
ci_providerNoTarget CI pipeline platform.github

Output Schema

NameRequiredDescriptionDefault
summaryYesDeterministic Markdown response summary.
airgappedYesWhether air-gapped silicon guidance was included.
stepCountYesNumber of progressive rollout stages.
canonicalUrlYesCanonical documentation or twin URL for citation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 a closed-world scope, so the description's 'read-only' label is largely redundant. It does add real context by disclosing the guide's four-phase content (X-Ray baseline, stealth Branch Guard, CI SARIF, isolated Git worktrees) and that output is tailored by LOC/languages/air-gap, but says nothing about latency, limits, or prerequisites. Useful additions, though the annotations carry most of the load.

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?

Front-loads purpose, then the example, then usage and exclusion — a sensible order with no filler sentences. The inline 'Example: ...' interrupts the flow slightly, but it earns its place by showing argument-to-output mapping.

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?

With an output schema present, the description need not explain return structure, and all four parameters are documented in the schema with defaults. Annotations cover the safety profile, and the description adds scope, content, and routing guidance — nothing an agent needs in order to call this 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% with per-parameter descriptions, defaults, bounds and examples, so the baseline applies. The description's example (languages=['go','typescript'], repo_loc=120000 → phased brownfield guide) hints that inputs shape the output, but it never explains how airgapped or ci_provider alter the plan, and the example duplicates one already in 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 and resource ('Retrieve a read-only 4-step Nomos rollout guide') and enumerates the four phases it contains, so an agent knows exactly what comes back. It also names the sibling it is not (scaffold_nomos_config) and the differentiating condition, making confusion between the two unlikely.

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?

Explicit when-to-use ('planning rollout steps for a team or monorepo') and an explicit when-not with the named alternative ('previewing raw nomos.yaml and CI workflow templates — use scaffold_nomos_config 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.