Skip to main content
Glama

Check Memoria Health

health
Read-onlyIdempotent

Check Memoria engine operational status, storage availability, tier distribution, and cloud sync mode to diagnose memory service issues.

Instructions

Return Memoria engine health, storage status, tier distribution, and cloud sync mode.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/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 openWorldHint=false, so the safety profile is fully covered. The description adds what the response will contain (storage status, tier distribution, cloud sync mode), which is genuine value, but says nothing about freshness, cost, failure behavior, or whether it touches the remote sync service.

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 or repetition; every phrase names concrete content the caller receives.

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 output schema, and complete annotations, the only burden on the description is conveying what comes back, and it enumerates four categories. It stops short of any detail on field shapes or whether the cloud sync mode reflects live state, which keeps it from a 5.

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 the baseline of 4 applies; there is no parameter meaning the description could add or omit.

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') and resource ('Memoria engine health') plus four enumerated data categories: storage status, tier distribution, cloud sync mode. That is enough to distinguish it from a generic 'stats' sibling, though it does not explicitly state how it differs from 'stats'.

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 by the name and content: an agent can infer this is a diagnostic probe to run before or after other operations. There is no explicit when-to-use statement and no exclusion naming 'stats' or any other sibling as the alternative for pure metrics.

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