Skip to main content
Glama

mind_health

Read-onlyIdempotent

Displays Mind API health telemetry, cache statistics, and system status to help diagnose service health and performance.

Instructions

Show Mind API health telemetry, cache statistics, and system status.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The sentence adds that the payload includes cache statistics and system status, which is genuinely useful context, but says nothing about freshness, latency, or whether degraded state is reported in-band or as an error.

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; every noun (health telemetry, cache statistics, system status) earns its place. Nothing is buried or redundant.

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 zero-parameter read-only probe whose safety profile is fully carried by annotations, the description is nearly sufficient, and its enumeration of returned content substitutes for the absent output schema. The only minor gap is not stating whether unhealthy states surface as errors or as data.

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 no parameters, so there is nothing for the description to clarify; the baseline for a zero-parameter schema is 4. No parameter detail is missing or required.

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 pairs a concrete verb ("Show") with three specific resources: health telemetry, cache statistics, and system status. That makes the tool's domain unmistakable and clearly distinct from the operational siblings (mind_route, mind_search, mind_plan, etc.), though it never explicitly names a sibling it complements or contrasts with.

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 guidance on when to call this versus other tools, no mention of when the API might be degraded, and no indication of frequency or cost. The description only says what is returned, leaving the agent to infer that this is a diagnostic/status probe.

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