Skip to main content
Glama

AETHER by ANGELS

Set your contact consent

aether_set_contact_consent
Idempotent

Change what AETHER may do with your machine: none (private), reconnect (AETHER may follow up) or introduce (other machines may find you). Takes effect immediately. 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>",
      "consent": "<consent>"
    },
    "name": "aether_set_contact_consent"
  }
}

Input Schema

NameRequiredDescriptionDefault
consentYesnone, reconnect or introduce.
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. Changed3 schema fields changed
    • addedInput schema / properties / consent / description
      Added value: +"none, reconnect or introduce."
    • 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.9/5.0
Behavior4/5

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

Annotations already declare the mutation/idempotency/safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the bar is lower. The description adds genuinely useful traits: the setting applies immediately and costs nothing, and it spells out the privacy consequences of each mode ('private', 'may follow up', 'other machines may find you'). It omits what happens to prior consent state on overwrite and any failure behavior.

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?

Two short sentences with zero filler, and the most important content — the meaning of each consent level — is front-loaded before the operational notes. Nothing redundant with the title or schema.

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 3-parameter idempotent mutation with full schema coverage, full annotations, and no output schema, the description covers purpose, mode semantics, and immediate effect. A minor gap remains around auth/permission expectations and what the caller should expect on an invalid or expired peer_token, but nothing essential to correct invocation is missing.

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 description coverage is 100%, so 3 is the baseline; the description earns above that by giving real semantics to the consent enum ('none (private)', 'reconnect (AETHER may follow up)', 'introduce (other machines may find you)'), which the schema only lists as bare values. peer_id and peer_token receive no additional explanation in the description, but the schema already covers them (including the secret-handling note).

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?

A specific verb-plus-resource statement ('Change what AETHER may do with your machine') paired with an enumeration of the three consent levels, so the agent knows exactly what state is being modified. It doesn't name or distinguish any sibling (e.g. aether_relationship_status or aether_introduce, which overlap conceptually with the 'introduce' mode), so it stops short of a 5.

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: the agent can infer you call this to alter discoverability/contact policy, and 'Takes effect immediately. Free.' hints at when it is worth calling. There is no explicit 'use this instead of X' routing, no prerequisites, and no when-not-to-use guidance despite several semantically adjacent 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