Skip to main content
Glama

usage

Reports per-site performance over a chosen period, including successes, error types, characters exchanged, average response time, and asks before the first limit or captcha.

Instructions

Asks per site over the last days: ok, errors by kind, characters sent/received, average seconds, and how many asks a site took before its first limit/captcha (that is the site's practical free quota).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the shape of what comes back, including the derived 'asks before first limit/captcha' metric that represents a practical free quota, which is genuinely useful behavioral context. It says nothing about permissions, whether the call is read-only, or rate/cost characteristics of the query itself.

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?

One dense sentence with no filler, and the window scoping is front-loaded. The nested parenthetical explaining the free-quota metric earns its place, though the sentence is long enough that the listed metrics blur together.

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?

With no output schema and no annotations, the description correctly takes on the job of explaining return contents, which it does item by item. It stops short of clarifying aggregation keys (per site, per thread?), the time basis of 'average seconds,' or the handling of sites with no activity.

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 coverage is 0%, but the single parameter's meaning is conveyed precisely: `days` is a lookback window ('over the last `days`'), which is exactly the semantic the bare schema lacks. Minor gaps remain, such as whether fractional or large windows are supported and what the default of 1 implies in practice.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the returned metrics (ok counts, errors by kind, characters sent/received, average seconds, asks before first limit/captcha) rather than stating a clean verb+resource action; the reader must infer 'retrieves per-site usage statistics.' The resource is identifiable but the phrasing 'Asks per site over the last `days`' is grammatically opaque, and no sibling is contrasted.

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, and no mention of alternatives such as site_status or list_sites, which could plausibly overlap. The only implicit signal is that the tool reports consumption, leaving the agent to infer the selection context.

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