Skip to main content
Glama

Get Namespace Statistics

stats
Read-onlyIdempotent

Inspect a namespace to return detailed memory, edge, and tier metrics for monitoring and analysis.

Instructions

Return detailed memory, edge, and tier statistics for a namespace.

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

Input Schema

NameRequiredDescriptionDefault
namespaceYesNamespace to inspect.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and a closed-world scope, so the safety profile is fully covered without the description. The description adds only the dimension of the returned data (memory, edge, tier), with no mention of cost, latency, size limits, or whether missing namespaces error out.

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?

A single front-loaded sentence with no filler, hedging, or redundancy. Every word carries information about the verb, the resource, and the metric families returned.

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?

For a one-parameter, read-only, annotated tool with full schema coverage and no output schema, the description supplies enough to call it correctly and to know roughly what comes back. It falls short only on guidance about when to prefer it over other diagnostic tools.

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?

With a single parameter at 100% schema description coverage, the schema already explains that 'namespace' identifies what to inspect. The description reinforces that statistics are computed over the namespace but adds no format, naming convention, or default behavior beyond the schema.

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 gives a specific verb ('Return') plus the resource ('statistics for a namespace') and scopes the content to memory, edge, and tier metrics. It is clear what the tool produces, though it does not distinguish itself from potentially adjacent diagnostic siblings such as 'health'.

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 explicit when-to-use or when-not-to-use guidance and no named alternative. An agent must infer that this is the inspection tool for a namespace's aggregate metrics, and cannot tell from the text how it differs from other diagnostic-style siblings.

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