Skip to main content
Glama

stats

Counts events per label value across project sources and compares the current window to the previous one, listing largest changes first so you know what moved before opening an entity.

Instructions

Counts per value of the label by over the project's sources, the last window against the window before, largest change first. where {label: value} narrows the events counted, sources narrows the sources. Use it to see what moved before reading one entity.

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": {
      "by": "<by>"
    },
    "name": "stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
byYes
topNo
whereNo
windowNo30m
projectNo
sourcesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.6/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 disclosure burden; it does useful work by revealing the comparison window, the largest-change-first ordering, and the narrowing semantics of `where` and `sources`. It never states that this is a read-only aggregate, doesn't mention how `top` truncates the result, and says nothing about permissions or result size.

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?

Three compact sentences, front-loaded with what is counted and how it is ranked, then filters, then the usage cue. Dense and mostly waste-free, though reusable parameter notation is packed into the middle sentence rather than separated out.

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?

For a 6-parameter, annotation-free aggregation tool the description covers the interesting semantics, and an output schema exists so return values needn't be described. The gaps around `top` truncation and `project` scoping leave the caller guessing on two parameters that materially affect results.

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 coverage is 0% across 6 parameters, so the description must compensate. It explains `by`, `window`, `where` (with the {label: value} shape) and `sources` well, but leaves `top` and `project` undocumented beyond incidental mentions ('the project's sources'), so a caller can't tell what `top` limits or how `project` scopes.

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 verb and resource — counting events per value of the `by` label across a project's sources — plus the comparative framing (last `window` vs. the window before, largest change first). It implicitly distinguishes itself from single-entity reads via 'before reading one entity', but doesn't name any concrete sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use it to see what moved before reading one entity' gives a clear usage context and sequencing cue relative to drill-down tools. It stops short of explicit when-not conditions or named alternatives.

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