Skip to main content
Glama

SophiaLabs & Nomos Open-Core MCP

recommend_adoption_plan

Read-onlyIdempotent

Generate a zero-risk Nomos onboarding plan (nomos xray, Branch Guard, CI SARIF, worktrees, or air-gapped GPU) tailored to repository scale.

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

Input Schema

NameRequiredDescriptionDefault
repo_locNoApproximate lines of code
airgappedNoSet true for zero-egress air-gapped local GPU setups
languagesNoRepository languages
ci_providerNoOptional CI system such as github or gitlab

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds the useful 'zero-risk' framing and the fact that the plan is scaled to repo size, but it does not describe the form of the returned plan or how the selected variant is chosen.

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 wasted clauses; the parenthetical variant list is dense but carries real information about supported plan types.

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?

All parameters are optional and annotated as a safe read, and the variant list hints at output content, but with no output schema the description should say more about what the generated plan looks like or how it is returned.

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 coverage is 100%, so all four parameters are already documented. The description only implicitly links 'repository scale' to repo_loc and 'air-gapped GPU' to airgapped, adding little meaning beyond the schema's own descriptions.

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 ('Generate') and resource ('Nomos onboarding plan') and enumerates the plan variants (nomos xray, Branch Guard, CI SARIF, worktrees, air-gapped GPU) plus the tailoring dimension (repository scale). It does not explicitly distinguish itself from the listed siblings, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the phrase 'onboarding plan' and 'tailored to repository scale' suggest this is for setting up Nomos in a repo, but there is no explicit when-to-use, when-not-to-use, or pointer to compare_governance_approaches or inspect_dod_gates as alternatives.

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.