Skip to main content
Glama

Usage stats & KPIs

stats
Read-only

Retrieve on-device operational KPIs—per-tool call counts, average latency, error counts, and reconciliation action distribution—to monitor this Vayl instance without data leaving the machine.

Instructions

Operational KPIs for this Vayl instance — on-device, nothing leaves the machine: per-tool call counts, average latency and error counts, plus the distribution of reconciliation actions the engine has taken (SUPERSEDE / RETRACT / FLAG / SKIP / ADD / …).

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": "stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the data is computed on-device and 'nothing leaves the machine,' which is a meaningful privacy guarantee an agent could not derive from annotations. It stops short of saying whether figures are cumulative-since-start or windowed, and whether the call is cheap or expensive.

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 sentence, front-loaded with the purpose and then the payload contents, with no filler. The trailing '…' after the action list is slightly loose but signals the enumeration is non-exhaustive, which is honest rather than wasteful.

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 an output schema present, the description needn't explain return shapes, and with zero parameters there is no input burden — so the definition is close to complete. The one substantive omission is the measurement window/aggregation basis, which matters for interpreting latency and error KPIs correctly.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The enumerated metric names do help an agent understand what the (schema-less) call yields, which is a small bonus.

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?

The description names the resource precisely (operational KPIs for this Vayl instance) and enumerates the concrete contents: per-tool call counts, average latency, error counts, and reconciliation action distribution. It is clearly a reporting/read tool, but it never explicitly distinguishes itself from siblings like health, audit_log, or history, which an agent could plausibly confuse it with.

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 for monitoring/observability, but there is no statement of when to call it versus health or audit_log, and no exclusions. With a zero-parameter tool the risk is low, but the guidance gap is real.

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