Skip to main content
Glama
Sign In
Smart Quota Orchestrator

Smart Quota Orchestrator

by ElNeMeR70
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

sqo_benchmark

Run live empirical token-compression benchmarks on a workspace and return measured before-vs-after savings.

Instructions

Run live empirical token-compression benchmarks on a workspace and return measured Before-vs-After savings.

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

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace path to benchmark.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv13.0.0

TDQS

A3.5/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 it does disclose that the run is live and empirical rather than a cached or estimated figure. It says nothing about runtime cost, whether the workspace is modified, or required permissions, which matters for a tool that executes real measurement work.

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?

A single sentence with the action and the output front-loaded and no filler. Nothing could be trimmed without losing the live/empirical distinction or the savings framing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter measurement tool with no output schema, the description covers what it acts on and what it returns at a high level. It could say more about how long a run takes or what the savings output looks like, but nothing essential for invoking it is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the single required 'workspace' parameter, so the schema does the explanatory work. The description adds no format or path-convention detail, which is acceptable at a one-parameter baseline.

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: running live empirical token-compression benchmarks on a workspace and returning measured Before-vs-After savings. That is clearly distinct from a tool that merely compresses a prompt, though it never names a sibling to contrast with.

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 reach for this versus the compression or context-health siblings, and no stated preconditions. The word 'benchmark' hints that this measures rather than applies compression, but the agent must infer that distinction.

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