Skip to main content
Glama
Smart Quota Orchestrator

Smart Quota Orchestrator

by ElNeMeR70

sqo_repo_dna

Compress an unfamiliar codebase into a dense repository DNA brief covering stacks, entrypoints, key modules, database schema, HTTP routes, and environment keys to quickly orient AI coding agents.

Instructions

Single-Shot <420-Token Repository Genome Synthesizer (v12.0 Quantum): compresses an entire unfamiliar codebase (stacks, entrypoints, top 5 gravity modules, DB ER genome, HTTP routes, env keys) into 1 ultra-dense strand (-99.2% vs Repomix dumps!).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace": "<workspace>"
    },
    "name": "sqo_repo_dna"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace root directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv13.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose useful behavioral traits: single-shot execution, a hard output budget (<420 tokens), and the compression ratio, which tell an agent the result will be terse. It omits whether the operation is read-only, how much of the filesystem is scanned, runtime/cost implications, and where the result goes.

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 the scope stated first, so an agent gets the gist immediately. However, marketing fragments ('v12.0 Quantum', '-99.2% vs Repomix dumps!') consume token budget without adding selection signal.

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?

There is no output schema, so the description must characterize the return value; it does list the sections but never states the format (markdown text, JSON, file artifact) or how an agent should read it. For a whole-repo synthesis tool, that is a meaningful remaining gap.

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?

With one required parameter and 100% schema description coverage, the schema already defines 'workspace' as the workspace root directory. The description adds no format, path-shape, or validation detail beyond 'entire codebase', so it neither compensates nor detracts.

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 concrete verb+resource ('compresses an entire unfamiliar codebase') and enumerates the contents of the output (stacks, entrypoints, top modules, DB ER, HTTP routes, env keys), which lets an agent predict the payload. It does not differentiate itself from near neighbors such as sqo_context_pack, sqo_api_routes or sqo_arch_diagram, and the 'Quantum/Genome' framing adds noise rather than precision.

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?

The phrase 'entire unfamiliar codebase' implies the intended situation (first-contact orientation on a repo you don't know), but there is no explicit when-to-use rule, no exclusions, and no pointer to the narrower sibling tools that cover single facets like routes or architecture diagrams.

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