Skip to main content
Glama
mcp-server-everesteer

mcp-server-everesteer

API health

get_health
Read-onlyIdempotent

Checks whether the Everesteer API service is healthy before workflows rely on it.

Instructions

Check whether the Everesteer API service is healthy.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/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 prose. The description adds only the fact that the check targets the Everesteer API service specifically; it says nothing about what 'healthy' means, error behavior, or rate limits, which is acceptable for a zero-parameter probe but not additive.

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 twelve-word sentence with no filler, and the resource scope is stated immediately rather than buried. Nothing in it is redundant or restating the title verbatim.

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 zero parameters, rich annotations, and an output schema that carries the return shape, the description covers everything needed to invoke the tool correctly. The only minor gap is guidance on interpreting or acting on an unhealthy result.

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 disambiguate and the baseline of 4 applies. The empty schema is consistent with the description's parameterless framing.

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 verb ('Check') plus a specific resource and scope ('whether the Everesteer API service is healthy'), which is enough to separate it from siblings like get_capabilities or whoami. It stops short of naming those siblings as alternatives, so it is clear but not differentiated by contrast.

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 word 'Check' — an agent can infer this is a liveness probe, but the description never says when to prefer it over get_capabilities or whoami, nor any precondition such as needing credentials or a reachable endpoint.

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