Skip to main content
Glama

Show usage counts

usage_counts
Read-only

Check whether anonymous usage counting is enabled and see exactly which metrics are counted and would be sent next, so you can verify privacy before proceeding.

Instructions

Anonymous usage counts: whether they're on and exactly what is counted and would be sent next.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), so the description's value is in disclosing content: it returns the enablement state, the enumerated data points counted, and a preview of the next payload. That 'would be sent next' framing is genuinely beyond what annotations convey and tells an agent this is a dry-run style report, not a transmission.

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?

A single compact sentence with the key concept front-loaded and no filler. It reads slightly awkwardly as a colon fragment rather than a sentence, which costs a point on structure.

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 parameters, no nested objects, and no output schema, the description carries the right amount: it explains what information comes back without needing to specify a return shape. Nothing an agent needs in order to call a zero-argument read tool correctly is absent.

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 of 4 applies and no parameter detail is missing.

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?

Names the resource (anonymous usage counts) and spells out the three things reported: whether counting is on, exactly what is counted, and what would be sent next. That clearly separates it from the mutating sibling set_usage_counts and from usage_choice, though the fragment-style phrasing ('Anonymous usage counts:') leaves the verb implicit in the title.

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?

The description never states when to reach for this tool versus set_usage_counts or usage_choice, nor any prerequisites. The read-only nature of inspecting a telemetry setting is only inferable from the siblings and annotations, not from the text itself.

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