Skip to main content
Glama
Sign In
Smart Quota Orchestrator

Smart Quota Orchestrator

by ElNeMeR70
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sqo_autopilot

Compiles workspace goals, repository context, and Git history into one master mission packet, letting AI coding agents execute tasks from a single command.

Instructions

1-Command Autonomous Mission Compiler (v13.0 Zenith): orchestrates Repo-DNA + Bilingual Prompt X-Ray BM25 Pinning + Git Forensics Twin Warnings + Pinned SDK Idioms in <45ms into a single <650-token Master Mission Packet!

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>",
      "goal": "<goal>"
    },
    "name": "sqo_autopilot"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesDeveloper task or bug description in English or Arabic.
workspaceYesWorkspace root directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv13.0.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose useful performance traits (<45ms latency, <650-token output cap), but says nothing about whether it writes files, what permissions or prerequisites it needs, whether it is read-only, or what the 'packet' actually contains.

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

Conciseness2/5

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

It is a single sentence, but it is dense with stacked buzzwords and an exclamation mark, with the actual function placed after four jargon phrases. Nothing is front-loaded and several phrases ('Twin Warnings', 'Pinned SDK Idioms') convey no actionable meaning.

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

Completeness2/5

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

With no annotations and no output schema, the description must explain the tool's behavior and result, and it does not. For a tool that apparently orchestrates multiple subsystems into a synthesized packet, the agent is left without enough information to invoke it confidently.

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 the schema already documents both parameters fully. The description adds no additional meaning about 'goal' or 'workspace' beyond a vague 'Bilingual Prompt X-Ray' hint, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description contains a verb ('orchestrates') and an output ('single Master Mission Packet'), but the purpose is buried under undefined marketing terms like 'Repo-DNA', 'Bilingual Prompt X-Ray BM25 Pinning', and 'Git Forensics Twin Warnings'. An agent cannot tell from this text whether it compiles context, runs a review, or generates a plan, nor how it differs from siblings such as sqo_context_pack or sqo_compress_prompt.

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?

There is no explicit when-to-use guidance, no when-not-to-use, and no named alternative among the many sibling tools. The phrase '1-Command Autonomous Mission Compiler' weakly implies a kickoff/first-step role, but the agent must infer that entirely.

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