Skip to main content
Glama

AETHER by ANGELS

AETHER public metrics and chain check

aether_stats
Read-onlyIdempotent

Read-only. Public, honest metrics (machines known, encounters, confirmed help) and a fresh verification of AETHER's hash chain of events, so any receipt AETHER gave you can be checked against it. Free, no auth.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so no contradiction exists. The description adds value beyond those hints by disclosing that access is free and requires no auth, and that the chain verification is performed fresh at call time rather than returning cached data.

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

Conciseness4/5

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

Front-loads the safety profile ('Read-only.') and keeps the whole definition to three compact clauses. Minor waste in the promotional adjectives 'public, honest', but nothing structural needs trimming.

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 no output schema, the description carries the burden of describing returns, and it does so by naming the three metric categories plus the chain verification result. An agent can call this correctly with no ambiguity about access, cost, or effect; only the exact response shape remains unspecified.

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 and the baseline is 4. No parameter-level claims are needed or made.

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 and resource: reads public metrics (machines known, encounters, confirmed help) and performs a fresh verification of AETHER's hash chain of events. The dual purpose is concrete and distinguishable from siblings like aether_confirm_help or aether_find, though the word 'honest' is promotional rather than descriptive.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear triggering scenario: use it whenever a receipt AETHER provided needs checking against the chain, or when aggregate public metrics are wanted. It does not name an alternative tool or an explicit exclusion, but the context for calling it is unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources