Skip to main content
Glama
Sign In
Smart Quota Orchestrator

Smart Quota Orchestrator

by ElNeMeR70
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sqo_verify_work

Audit git diffs to catch TODO/placeholder laziness, silent public symbol deletions, out-of-scope file creep and bloat; returns a 0-100 Surgical Discipline Score.

Instructions

Executable Andrej Karpathy + Superpowers Diff Gatekeeper (v10.0): audits git diffs for TODO/placeholder laziness, silent public symbol deletions, out-of-scope file creep, and bloat, returning a 0-100 Surgical Discipline Score.

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_verify_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
diff_textNoOptional unified diff override.
workspaceYesWorkspace root directory.
allowed_filesNoOptional list of allowed file/folder scopes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv13.0.0

TDQS

B3.2/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 the audit dimensions and the return value (a 0-100 Surgical Discipline Score), which is real behavioral context, but it omits whether the tool is read-only, what score thresholds mean, whether it blocks or merely reports, and how the score is computed.

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 that names the checks and the output. It is efficient, but the 'Executable Andrej Karpathy + Superpowers Diff Gatekeeper (v10.0)' branding consumes space without informing an agent.

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?

For a 3-parameter tool with no output schema and no annotations, the description covers what is checked and what is returned, but leaves gaps on score interpretation, read-only safety, and failure behavior that an agent would need to use the result correctly.

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 description coverage is 100%, so all three parameters (diff_text, workspace, allowed_files) are already documented in the schema. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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 and resource: audits git diffs for four named defect classes (TODO/placeholder laziness, silent public symbol deletions, out-of-scope file creep, bloat) and returns a 0-100 score. The 'Diff Gatekeeper' framing plus the enumerated checks make it distinguishable from siblings like sqo_verify_deps or sqo_dead_code, though the branding prefix ('Executable Andrej Karpathy + Superpowers ... v10.0') adds noise rather than clarity.

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 guidance on when to invoke this versus alternatives, no prerequisites, and no exclusions. The description never says whether this should run before commit, in CI, or on demand, nor how it relates to sibling verification tools.

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