Skip to main content
Glama

other_get_health

Read-onlyIdempotent

Check Aeza API health status to confirm service availability and diagnose connectivity issues before managing servers, backups, networks, DNS, billing, or support.

Instructions

Other get health GET /health

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered without the description. The description adds nothing beyond that — no note on whether the call is rate-limited, unauthenticated, expensive, or what a failure/success indicates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short lines with no padding, so it is certainly concise. However, the first line duplicates the tool name verbatim and the second is a bare route string, meaning nearly every token is redundant rather than informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (no params, no output schema, no nesting), which lowers the bar, but with no output schema the description should at least hint at what a health check returns or what states are possible. As written, an agent knows the route but not what a result means.

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 (additionalProperties: false, empty properties), so there is no parameter semantics to explain. Baseline of 4 applies since the description cannot and need not add parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Other get health" essentially restates the tool name, and the only extra content is the raw route "GET /health". It never explains what "health" refers to — liveness of the API, status of the account, or something else — so an agent must infer the resource from the endpoint path alone.

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?

No explicit when-to-use guidance, no prerequisites, and no mention of the sibling diagnostic tools (other_get_errors, other_get_info, other_get_version) that an agent might choose instead. The only signal is the implied convention that a /health endpoint is for checking service availability.

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

Deploy Server

Other Tools