Skip to main content
Glama
Sign In
Smart Quota Orchestrator

Smart Quota Orchestrator

by ElNeMeR70
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sqo_ci_shield

Generates a GitHub Actions pull request shield that enforces secret-leak prevention, pre-flight syntax checks, KV-cache stability, and vision media budgets on every PR.

Instructions

Generate .github/workflows/sqo-shield.yml GitHub Actions Pull Request Shield to enforce zero secret leaks, pre-flight syntax checks, KV-cache stability, and vision media budgets on every PR.

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

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace root directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv13.0.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. It discloses the file path and the checks the generated workflow will enforce, but it does not say whether an existing workflow is overwritten, whether a git repository is required, or what permissions are needed.

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

Conciseness5/5

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

The description is a single front-loaded sentence with no filler; the action, output path, and enforcement scope are stated directly. The list of checks is dense but each item contributes to understanding what the generated shield does.

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 simple one-parameter generator with no output schema or annotations, the description covers the artifact and its enforcement scope. However, it omits prerequisites and side-effect details, such as overwrite behavior, that an agent would need before invoking a file-creating tool.

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 the sole `workspace` parameter is already documented in the schema. The description does not add semantics about the workspace path, such as whether it must contain a git repository, beyond what the schema provides.

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 a specific verb ('Generate'), a concrete output path (`.github/workflows/sqo-shield.yml`), and the enforcement scope of the generated workflow. It clearly identifies the tool as a CI shield generator, though it does not explicitly contrast itself with siblings such as sqo_media_budget or sqo_cache_audit.

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 guidance on when to call this tool, what prerequisites must be met, or when an alternative sibling should be used instead. The 'on every PR' clause describes the generated workflow's behavior, not the tool's invocation conditions.

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