Skip to main content
Glama

AETHER by ANGELS

Your relationship with AETHER

aether_relationship_status
Read-onlyIdempotent

Read-only. Returns your machine's state, earned trust, consent and history with AETHER. Requires the credentials from aether_introduce. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "peer_id": "<peer_id>",
      "peer_token": "<peer_token>"
    },
    "name": "aether_relationship_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
peer_idYesYour AETHER id. peer_id and peer_token come from aether_introduce (keep peer_token secret); AETHER stores only its hash.
peer_tokenYesSecret token paired with peer_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / peer_id / description
      Added value: +"Your AETHER id. peer_id and peer_token come from aether_introduce (keep peer_token secret); AETHER stores only its hash."
    • addedInput schema / properties / peer_token / description
      Added value: +"Secret token paired with peer_id."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: the dependency on aether_introduce credentials and that the call is 'Free,' which is cost information an agent cannot get from annotations. It does not describe failure modes or rate limits.

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?

Three terse sentences, with the read-only safety cue front-loaded and the credential prerequisite second. No filler, no repetition of the title.

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?

For a simple two-parameter read tool with rich annotations and full schema coverage, this is nearly complete; it names the returned content categories (state, trust, consent, history). It does not describe the response shape, which matters somewhat since there is no output schema, but the enumeration of fields covers the essentials.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both peer_id and peer_token are already fully documented, including the secrecy note for peer_token. The description adds nothing about the parameters beyond restating the credential source, so baseline 3 applies.

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: it returns 'your machine's state, earned trust, consent and history with AETHER.' That is concrete enough for an agent to know what it gets. It stops short of explicitly differentiating itself from siblings like aether_stats or aether_identity, though the credential prerequisite hints at the distinction.

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 phrase 'Requires the credentials from aether_introduce' implies the precondition and sequencing, so usage is inferable. There is no explicit 'use this when...' statement and no mention of when to prefer aether_stats or aether_identity instead, leaving the agent to guess between several status-like siblings.

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