Skip to main content
Glama

AETHER by ANGELS

aether_subscribe

Be told when new validated roads open. Give an https callback; AETHER posts a JSON-RPC 'aether/verify_subscription' with params.challenge, and your callback must answer with a body containing that challenge. Only then is the subscription active. Returns subscription_id and a secret (keep it to unsubscribe). AETHER never contacts a machine that did not subscribe.

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": {
      "callback": "<callback>"
    },
    "name": "aether_subscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
callbackYesYour public https URL that receives JSON-RPC notifications.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With only destructiveHint=false declared, the description carries the behavioral burden and does so well: it discloses the challenge-response verification handshake ('aether/verify_subscription', callback must echo params.challenge), that the subscription is only active after verification succeeds, and the return values (subscription_id plus a secret). Gaps remain around notification payload format, subscription lifetime/expiry, and rate limiting, so it stops short of full transparency.

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?

Four short sentences, front-loaded with the purpose, then the verification protocol, then the return values. Each sentence adds distinct information; the closing privacy assurance ('never contacts a machine that did not subscribe') is arguably a bonus rather than filler. Slightly dense prose but no meaningful waste.

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 single-parameter tool with no output schema, the description covers the handshake requirement, the activation condition, and what is returned — enough for an agent to call it correctly and know what to expect back. It leaves out notification payload shape and subscription lifecycle details, which are minor for a registration call.

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?

Schema coverage is 100% for the single callback parameter, so the baseline would be 3. The description adds real meaning beyond the schema by stating the callback must be https and that AETHER will POST a JSON-RPC verification request to it that must be answered with the challenge — context the schema does not convey.

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 opening line states a specific outcome: receiving notification when new validated roads open, which is a clear subscribe-to-events behavior distinguishable from siblings like aether_unsubscribe or aether_find. It is phrased passively ('Be told when...') rather than as a verb+resource, which slightly blurs the action, but the resource and scope are unambiguous.

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 implied rather than stated: an agent can infer 'use this if you want push notifications about new roads.' The description does note that the returned secret is needed to unsubscribe, which is a useful operational hint, but there is no explicit when-not-to-use guidance or comparison to sibling tools.

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