Skip to main content
Glama
Smart Quota Orchestrator

Smart Quota Orchestrator

by ElNeMeR70

sqo_repo_badge

Generate a verified SVG shield badge showing a repository's measured token reduction percentage and prompt-tax grade for quick quota-health visibility.

Instructions

Generate a verified Smart Quota OS SVG shield badge (sqo-badge.svg) displaying the repository's empirical token reduction % and prompt-tax grade.

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

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace root directory.
output_pathNoOptional output SVG file path (default: sqo-badge.svg in workspace).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv13.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and falls short: it does not say whether an existing `sqo-badge.svg` is overwritten, whether the tool writes to disk at all versus returning markup, or what permissions/inputs it needs. The only behavioral fact surfaced — the artifact name and its two displayed metrics — is already largely implied by the tool name and the schema's default output_path.

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 naming the verb, the artifact, and its contents, with no filler. It is efficient, though it spends its words on output description at the expense of any usage or behavior guidance.

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?

The tool is simple (two params, no output schema, no nesting), so the description needn't explain return values in depth. However, for a file-writing generator it omits whether prior analysis is required and how it handles an existing badge file, which are the details an agent most needs before invoking it.

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%, with both `workspace` and `output_path` documented in the schema, including the default filename. The description adds no new meaning to either parameter (no format constraints on output_path, no clarification of what workspace root means for this tool), so the baseline 3 applies.

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 gives a specific verb and artifact: it generates an SVG shield badge file (`sqo-badge.svg`) and states exactly what the badge displays (token reduction % and prompt-tax grade). An agent can tell this is a reporting/visualization tool, though it never distinguishes itself from siblings like sqo_repo_dna or sqo_benchmark that might also surface metrics.

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 when-to-use guidance, no prerequisites (e.g. whether repository analysis must run first), and no alternatives named. The description only states what the tool produces, leaving the agent to infer the context in which a badge should be generated rather than, say, a full report.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.