Skip to main content
Glama
Sign In
Smart Quota Orchestrator

Smart Quota Orchestrator

by ElNeMeR70
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sqo_checkpoint

Create zlib-compressed source snapshots, diff live edits against a checkpoint, and roll back selected files without touching Git history.

Instructions

Zero-Git-Conflict Session Time-Machine: create instant zlib-compressed source snapshots, diff live edits against a checkpoint, or surgically roll back files without touching Git history.

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": {
      "action": "<action>",
      "workspace": "<workspace>"
    },
    "name": "sqo_checkpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesNoOptional relative file subset to snapshot or restore.
labelNoCheckpoint label when action='create'.
actionYesCheckpoint action.
workspaceYesWorkspace root directory.
checkpoint_idNoCheckpoint ID (or 'latest') for diff/restore.

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 disclosure burden. It usefully states that snapshots are zlib-compressed and independent of Git history, but omits critical behavior for a mutation tool: whether 'restore' overwrites current file contents, whether it is reversible, what happens to files not in a checkpoint, and where checkpoints are stored or how much space they consume.

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?

It is a single dense sentence with no filler clauses. The one weakness is front-loading a marketing label ('Zero-Git-Conflict Session Time-Machine') ahead of the actual operation verbs, which delays the actionable content slightly.

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 5-parameter, no-annotation, no-output-schema tool that includes a destructive-sounding restore, the definition should say more about restore semantics, storage location, and failure modes. It covers the happy path of each capability but leaves the agent without enough to call 'restore' safely.

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 five parameters are already documented, establishing a baseline of 3. The description adds compression and Git-independence context but no parameter-level detail beyond the schema, and it enumerates create/diff/restore while silently skipping the 'list' action that the action enum defines.

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?

The description names concrete verbs and resources: create zlib-compressed source snapshots, diff live edits against a checkpoint, roll back files. The 'without touching Git history' clause implicitly separates it from version-control siblings like sqo_git_forensics, though no sibling is named. Only the 'list' enum action goes unmentioned, a small gap.

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?

Usage is only implied — the 'Zero-Git-Conflict' framing and 'without touching Git history' suggest when a checkpoint beats Git, and 'roll back files surgically' hints at restore scenarios. There is no explicit when-to-use/when-not guidance, no prerequisites, and no mention of how to choose among the four actions beyond the schema enum.

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