Skip to main content
Glama

Nomos - Deterministic Git & AST Governance for AI Coding Agents

Inspect Public GitHub Repo AST X-Ray

xray_github_repo
Read-onlyIdempotent

Inspect a public GitHub repository via read-only static Tree-sitter AST analysis (<= 100MB source archive, strictly read-only) to retrieve its AI Hangover Score (0-100), complexity hotspots, and Day-0 baseline preview. Example: repo='go-chi/chi' returns the AST scorecard for go-chi/chi. Use when auditing a public GitHub owner/repo URL. Do NOT use when checking private repositories (private codebases require local CLI inspection via @mgantlett/nomos).

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": "go-chi/chi"
    },
    "name": "xray_github_repo"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesPublic GitHub owner/repo slug or full https://github.com/<owner>/<repo> URL.

Output Schema

NameRequiredDescriptionDefault
repoYesNormalized owner/repo slug.
gradeNoStructural health grade.
summaryYesDeterministic Markdown response summary.
canonicalUrlYesCanonical documentation or twin URL for citation.
hangoverScoreNoComposite 0-100 AI Hangover structural debt score.

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 readOnly/openWorld/idempotent/non-destructive, and the description adds real context on top: a 100MB source-archive ceiling, static (non-executing) analysis, and that private code must go through a local CLI. It does not mention rate limits, latency, or caching, so it stops short of full behavioral disclosure.

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?

Purpose and return values are front-loaded, and the usage exclusion is sequenced last where it belongs. There is minor redundancy in repeating 'read-only' twice and the 'Strictly read-only' parenthetical back-to-back, which costs a bit of density.

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 one-parameter, read-only inspector with an output schema, the description covers scope, method, size limits, return content, and the private-repo exclusion. Nothing an agent needs to decide or call 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 coverage is 100% and the single 'repo' parameter already documents its accepted formats (owner/repo slug or full GitHub URL) plus length bounds. The description only restates this with a worked example ('repo=go-chi/chi'), adding illustration but no new meaning 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?

States a specific verb and resource ('Inspect a public GitHub repository') and names exactly what comes back: AI Hangover Score (0-100), complexity hotspots, and a Day-0 baseline preview. It also pins the method (read-only static Tree-sitter AST analysis), which tells an agent how results are produced versus a live-runtime probe.

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 an explicit positive trigger ('Use when auditing a public GitHub owner/repo URL') and an explicit exclusion ('Do NOT use when checking private repositories') with the named alternative (@mgantlett/nomos local CLI). The when/when-not/alternative triad is fully present.

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.