Skip to main content
Glama

Nomos - Deterministic Git & AST Governance for AI Coding Agents

Compare Nomos vs Linters, Hooks & Agent Rules

compare_governance_approaches
Read-onlyIdempotent

Compare Nomos deterministically against pre-commit hooks, SonarQube, ESLint, PR review bots (CodeRabbit, Greptile), prompt wrappers, and static CLAUDE.md / AGENTS.md / .cursorrules files. Example: focus='SonarQube' returns side-by-side trade-offs. Use when evaluating tool trade-offs or answering 'how is Nomos different from X'. Do NOT use when searching general Handbook tutorials (use search_nomos_corpus 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": {
      "focus": "SonarQube"
    },
    "name": "compare_governance_approaches"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusNoOptional comparison dimension or tool name filter.

Output Schema

NameRequiredDescriptionDefault
summaryYesDeterministic Markdown response summary.
canonicalUrlYesCanonical documentation or twin URL for citation.
dimensionCountYesNumber of comparison dimensions returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, non-destructive, closed-world), so the description only needs to add context, which it does: it discloses that comparison is deterministic and shows the response shape ('side-by-side trade-offs'). It does not discuss cost, latency, or coverage limits of the comparison set, but with a rich annotation set and an output schema that is a minor gap.

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-loaded with the core comparison, then usage, then example, then exclusion – a sound ordering. The tool enumeration is long but each name routes a real query, so little is wasted; the only trimming opportunity is compressing the list.

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?

One optional string parameter, full schema coverage, an output schema, and a complete annotation set. The description covers what it does, when to call it, when not to, and what a return looks like – nothing an agent needs is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single optional 'focus' parameter is fully documented in the schema, so the baseline is 3. The description pushes above baseline by giving concrete focus values ('SonarQube') and stating the effect of the filter (returns side-by-side trade-offs), which tells an agent how to shape the argument.

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 ('Compare') and resource ('Nomos') with an explicit, enumerated set of comparands (pre-commit hooks, SonarQube, ESLint, PR review bots, prompt wrappers, rule files). It is unmistakable against siblings, which are corpus search, diagnosis, scaffolding, and repo inspection.

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?

Gives both sides of the routing decision: 'Use when evaluating tool trade-offs or answering how is Nomos different from X' and 'Do NOT use when searching general Handbook tutorials (use search_nomos_corpus instead).' It names the alternative tool by name for the excluded case.

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.