Confirm API connectivity by probing health status, so MCP hosts can verify Aureon MCP is reachable before operations.
Health probe — confirms API connectivity
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": "aureon_ping"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.16Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It conveys the essential trait a non-mutating connectivity check but says nothing about auth requirements, rate limits, or what a failed probe looks like. For a zero-parameter probe the burden is small, so this is adequate but thin.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with zero filler; the purpose is stated before the elaboration. Nothing redundant or padded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description should ideally indicate what a successful probe returns (status payload, version, latency). It only asserts that connectivity is confirmed, leaving the response shape unspecified. Otherwise complete for a trivial probe.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes no parameters, so no parameter semantics are needed; the baseline for a zero-parameter tool is 4. The description correctly implies no input is required.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb-and-resource (health probe / confirms API connectivity), so an agent knows exactly what it validates. It does not differentiate itself from the sibling aureon_get_health, which is a plausible overlap risk.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase health probe implies the usage context (liveness/connectivity check) without spelling out when to prefer it over aureon_get_health, aureon_registry_status, or aureon_get_vault_status. No explicit when-to-use or when-not-to-use guidance is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.