Skip to main content
Glama
Céu Natal

Céu Natal

Verificar o servidor

healthcheck
Read-onlyIdempotent

Verifies whether the Céu Natal server is operational and returns its version, helping confirm service availability.

Instructions

Verifica se o servidor está operacional e retorna a versão.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
statusYes
versaoYes
transporteYes
codigo_fonteYes
proximo_passoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.6

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds only that a version string is returned, which the output schema also covers. With annotations doing the heavy lifting, this is adequate but adds little extra context such as latency, side effects, or auth requirements.

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?

It is a single short sentence that front-loads the purpose and adds the return value, with zero wasted words. Nothing is buried or repeated.

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?

This is a simple, no-parameter probe whose annotations cover the safety profile and whose output schema documents the return value. The description is sufficient to call it correctly. A minor gap is that it does not say what a failure looks like or whether it is cheap to call frequently.

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 nothing for the description to disambiguate. The baseline for a parameterless tool applies, and the description correctly implies that no input is 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 states a specific verb and resource: it checks whether the server is operational and returns its version. That is unambiguous for an agent. It does not distinguish itself from siblings, but the siblings are all astrological calculation tools, so the distinction is obvious from the resource alone.

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?

The usage is only implied: an agent can infer this is a connectivity or liveness probe. There is no explicit statement of when to call it, such as before a batch of calculations, or when not to call it, and no named alternative. Minimum viable guidance.

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