Skip to main content
Glama

scope_stats

Read-onlyIdempotent

Retrieve per-day call and result-return counters for a named scope, newest first, to verify scope effectiveness and cost savings; unknown scopes return explicit errors.

Instructions

Per-day hit counters for one scope (calls, results_returned), most recent first — the cost-savings evidence (spec「Scope effectiveness is observable」). An unknown scope is an explicit error naming it.

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": {
      "scope_name": "<scope_name>"
    },
    "name": "scope_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
scope_nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds behavior not in the annotations: results are ordered most recent first and an unknown scope produces an explicit error naming the offending scope. That error contract is genuinely useful and slightly exceeds the annotation baseline.

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?

Two tight sentences, front-loaded with what is returned and in what order, followed by the error contract. The spec reference in brackets is mildly decorative but does not obscure anything.

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?

An output schema exists, so return values need no explanation, and annotations cover safety and idempotency. However, the days window semantics and any result-size limits are absent, which matters for a stats tool whose main risk is misinterpreting the time window.

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 0%, so the description must carry parameter meaning. It partially does: 'one scope' ties to scope_name and the unknown-scope error clarifies its validation behavior. The days parameter (default 30) is never explained, so the agent must guess whether it is a lookback window or a page size.

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 concrete return shape (per-day hit counters with the metrics calls and results_returned) scoped to one scope, ordered most recent first. That is a specific verb-plus-resource statement an agent can act on. It does not explicitly contrast with data_stats or scope_list, so sibling differentiation is left implicit.

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 through the phrase 'the cost-savings evidence', which hints at when this tool matters, but there is no explicit when-to-use or when-not-to-use statement. Nothing tells the agent whether to prefer data_stats or scope_list for related questions. Adequate minimum, with a clear gap.

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