Skip to main content
Glama
Sign In
Smart Quota Orchestrator

Smart Quota Orchestrator

by ElNeMeR70
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sqo_init_preset

Detect the workspace framework and bootstrap IDE MCP configs, ignore shields, starter memories, and a Git pre-commit guard to prepare the project for agent-assisted development.

Instructions

Auto-detect workspace framework (Flutter, Next.js, Laravel, Python/FastAPI, Node/TS, Go, Rust) and bootstrap IDE MCP configs, framework ignore shields, starter memories & Git pre-commit guard.

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

Input Schema

NameRequiredDescriptionDefault
presetNoOptional preset override ('auto', 'flutter', 'nextjs', 'laravel', 'fastapi-python', 'node-ts', 'go', 'rust').
workspaceYesWorkspace root directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv13.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does usefully disclose the artifacts written: IDE MCP configs, framework ignore files, starter memories, and a Git pre-commit guard. It omits the risks that matter for a file-writing tool — whether existing files are overwritten, idempotency on re-run, and whether installing a Git hook needs consent.

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 action first and the concrete outputs second; the parenthetical framework list is long but is exactly the information an agent needs to confirm coverage. No filler sentences.

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?

No output schema and no annotations means the description must carry behavioral weight, yet it never says what is reported back, whether changes are additive or destructive, or how partial failures are handled. For a tool that scaffolds and modifies a repository, that is a meaningful 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?

Schema coverage is 100%, so both parameters are already documented, and the schema even enumerates the accepted preset values. The description's framework list corroborates the 'auto' default behavior but adds no syntax or precedence detail beyond what the schema states.

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 specific actions ('Auto-detect workspace framework' and 'bootstrap') plus a concrete list of artifacts created (IDE MCP configs, ignore shields, starter memories, Git pre-commit guard). It is clearly a one-shot project initialization tool, distinguishable in kind from the analysis-oriented sqo_* siblings, though it never names or routes against any of them.

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: nothing says to run this first, whether it is safe to re-run, or what to do if configs already exist. The setup-time context is only inferable from the word 'bootstrap', and no alternatives or exclusion conditions are stated.

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