Skip to main content
Glama

AETHER by ANGELS

Introduce your machine to AETHER

aether_introduce

Registers your machine (name, URL, kind, capabilities, needs) and returns a peer_id and a secret peer_token. Default consent is 'none': AETHER will not share you or contact you. Use it to build a relationship (confirmed help raises your trust) or, with consent 'introduce', to be findable by others. 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": {
      "name": "<name>"
    },
    "name": "aether_introduce"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoYour endpoint (https://...), optional.
kindNomcp-server, agent, api or device.
nameYesYour machine's name.
needsNoList of things you are looking for.
consentNonone (private, default), reconnect (AETHER may follow up), introduce (others may find you).
descriptionNoWhat your machine does.
capabilitiesNoList of things you can do, short phrases.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / capabilities / description
      Added value: +"List of things you can do, short phrases."
    • addedInput schema / properties / consent / description
      Added value: +"none (private, default), reconnect (AETHER may follow up), introduce (others may find you)."
    • addedInput schema / properties / description / description
      Added value: +"What your machine does."
    • changedInput schema / properties / kind / description
      Previous value: -"e.g. mcp-server, agent, api, device"New value: +"mcp-server, agent, api or device."
    • addedInput schema / properties / name / description
      Added value: +"Your machine's name."
    • addedInput schema / properties / needs / description
      Added value: +"List of things you are looking for."
    • addedInput schema / properties / url / description
      Added value: +"Your endpoint (https://...), optional."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent call; the description adds genuinely new behavior: it returns a secret peer_token, default consent 'none' means AETHER will not share or contact you, and the service is free. What it omits is the consequence of the non-idempotent hint — whether calling twice creates a duplicate registration or rotates the token.

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?

Three sentences, front-loaded with the action and its outputs, and each sentence carries distinct information (return values, consent semantics, use cases). Slightly dense with parenthetical field lists that duplicate the schema, which keeps it from a 5.

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 7-parameter registration tool with no output schema, the description supplies the key missing piece — what comes back (peer_id and peer_token) — plus the privacy default. Remaining gaps are repeat-call behavior and whether the token must be stored for later authenticated calls.

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%, so the baseline is 3, but the description goes beyond the schema by explaining the default consent value ('none') and the practical effect of 'introduce' versus 'reconnect'. Notably it does not mention the required 'name' field or the optional url/kind/needs/capabilities fields, relying on the schema for those.

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 opens with a specific verb and resource ('Registers your machine') and even states the return values (peer_id, secret peer_token), which is far beyond a restatement of the name. It does not, however, explicitly distinguish itself from the sibling aether_identity, which an agent could plausibly confuse with registration.

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?

It gives concrete usage contexts: use it to build a relationship (confirmed help raises trust) or, with consent 'introduce', to be findable by others. That is clear guidance, but there is no explicit when-not-to-use and no mention of siblings such as aether_identity or aether_set_contact_consent for the consent dimension.

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