Skip to main content
Glama
Sign In
archiet-xray

archiet-xray

by Anioko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

production_readiness

Read-only

Score your repository's production readiness from 0 to 100 across 8 deterministic dimensions, with evidence per dimension and top fixes ranked by points lost.

Instructions

Score the repo's production readiness 0-100 across 8 deterministic dimensions (auth coverage, secrets hygiene, client token storage, data-layer discipline, test footprint, migration discipline, ops readiness, docs/API contract) with per-dimension evidence and the top fixes ranked by points lost. Same repo always scores the same.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.4

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description need not repeat safe read behavior. It adds valuable info about determinism ('Same repo always scores the same') and the output structure (8 dimensions, evidence, ranked fixes), which goes beyond the annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, information-dense sentence that leads with the core purpose, then enumerates the dimensions and outputs efficiently. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a no-parameter, read-only tool with no output schema, the description covers the essential behavior and output semantics. It could specify the target repo (implicitly the current repo) more explicitly, but this is a minor gap.

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?

The tool has zero parameters and the schema is empty (100% coverage). Per the rubric, the baseline is 4. The description does not need to explain parameters, and the low complexity is handled well.

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 clearly states the tool's function: 'Score the repo's production readiness 0-100' across 8 specific dimensions. It also distinguishes it from siblings by highlighting the deterministic nature and the structured output (per-dimension evidence, ranked fixes).

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

Usage Guidelines2/5

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

No explicit usage guidance or comparison to sibling tools is provided. The description does not state when to use this tool instead of alternatives like xray_scan or arch_summary, nor any exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools