Skip to main content
Glama

Memory statistics

padam_stats
Read-onlyIdempotent

Reports memory counts by status and type, pending owner reviews, consolidation status, active embedding backend, and database location.

Instructions

Current state of memory: counts by status and type, records waiting for the owner's review, whether consolidation is due, which embedding backend is active, where the database lives.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dbYes
selfYes
activeYes
attacksNo
backendYes
by_kindYes
revokedYes
dlpShieldNo
last_sleepYes
supersededYes
quarantinedYes
record_keysYes
hardwareSealNo
stale_vectorsYes
activeRootScopeNo
predictiveCacheNo
episodes_pendingYes
consolidation_dueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.2
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "active": {
      +      "type": "integer"
      +    },
      +    "activeRootScope": {
      +      "type": "string"
      +    },
      +    "attacks": {
      +      "type": "object"
      +    },
      +    "backend": {
      +      "type": "string"
      +    },
      +    "by_kind": {
      +      "type": "object"
      +    },
      +    "consolidation_due": {
      +      "type": "boolean"
      +    },
      +    "db": {
      +      "type": "string"
      +    },
      +    "dlpShield": {
      +      "type": "object"
      +    },
      +    "episodes_pending": {
      +      "type": "integer"
      +    },
      +    "hardwareSeal": {
      +      "type": "object"
      +    },
      +    "last_sleep": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "predictiveCache": {
      +      "type": "object"
      +    },
      +    "quarantined": {
      +      "type": "integer"
      +    },
      +    "record_keys": {
      +      "type": "object"
      +    },
      +    "revoked": {
      +      "type": "integer"
      +    },
      +    "self": {
      +      "type": "object"
      +    },
      +    "stale_vectors": {
      +      "type": "integer"
      +    },
      +    "superseded": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "backend",
      +    "db",
      +    "active",
      +    "superseded",
      +    "revoked",
      +    "quarantined",
      +    "episodes_pending",
      +    "consolidation_due",
      +    "stale_vectors",
      +    "by_kind",
      +    "record_keys",
      +    "self",
      +    "last_sleep"
      +  ],
      +  "type": "object"
      +}
  2. First observedv0.4.8

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds real behavioral content beyond that: it discloses the specific signals surfaced (pending-review backlog, consolidation due, active embedding backend, DB location), which an agent needs to decide whether follow-up actions are warranted.

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 beginning with the scope ('Current state of memory:') followed by a tight enumeration of reported items. Every clause names a distinct output dimension; there is no filler or repetition.

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 no-parameter, read-only tool with full annotations and an output schema, the definition is essentially complete. The enumerated return items partly duplicate the output schema, which is harmless but not strictly required, and no cost/latency or sibling-routing hint is given.

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 no parameter meaning to convey and the baseline of 4 applies. The description correctly stays silent on inputs rather than inventing any.

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 specific resource (current memory state) and enumerates exactly what is reported: status/type counts, records awaiting owner review, consolidation due, active embedding backend, and database location. An agent can tell this is the read-only diagnostic overview rather than a mutation tool like padam_write or padam_confirm, though it never names a sibling explicitly.

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?

There is no explicit when-to-use statement or exclusion of alternatives; the guidance is implied by 'current state' and the inventory of reported facts. An agent can infer this is the orientation/diagnostic call, but nothing tells it whether to prefer padam_profile, padam_timeline, or this tool first.

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