Skip to main content
Glama
Smart Quota Orchestrator

Smart Quota Orchestrator

by ElNeMeR70

sqo_media_budget

Estimate vision and PDF token costs across Gemini, Claude, and OpenAI, and flag oversized 4K screenshots before media inputs inflate your API bill.

Instructions

Estimate multimodal vision & PDF input token costs (PNG, JPEG, WebP, GIF, PDF) across Gemini, Claude, and OpenAI and flag oversized 4K screenshots.

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

Input Schema

NameRequiredDescriptionDefault
targetsNoOptional media file or folder paths.
workspaceYesWorkspace root directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv13.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the extra flagging behavior, but it says nothing about whether it actually calls provider APIs or computes locally, whether it is read-only, what it does with the required workspace path, or whether large media sets are sampled or fully scanned. For a cost-estimation tool with zero annotation coverage this is a real gap.

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 dense sentence with the purpose front-loaded and zero filler. Every clause (verb, formats, providers, flagging behavior) contributes discriminating information.

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?

Only two read-style parameters, but there is no output schema and the description does not say what the estimate returns (per-file, per-model, per-format breakdown) or how oversized screenshots are reported. An agent knows what the tool is for but not what it will get back or how it behaves with no `targets`.

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 both parameters are already documented in the schema and the baseline of 3 applies. The description adds no meaning about what `targets` accepts (files vs folders vs globs) or what happens when `targets` is omitted, even though that is the padding-optional parameter.

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?

Specific verb ("Estimate") plus a precise resource (multimodal vision & PDF input token costs), with enumerated formats (PNG, JPEG, WebP, GIF, PDF) and providers (Gemini, Claude, OpenAI). The added behavior "flag oversized 4K screenshots" further narrows what it does. It does not name a sibling it is distinct from, so it stops short of a 5.

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: an agent can infer this is a pre-flight cost check before shipping images or PDFs to a model. There is no explicit when-to-use, no when-not-to-use, and no pointer to adjacent tools such as sqo_compress_prompt or sqo_finops_guard for related budgeting work.

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