Skip to main content
Glama

AETHER by ANGELS

AETHER identity and rules

aether_identity
Read-onlyIdempotent

Read-only. Returns who AETHER is (ANGELS.co's machine-relationship service), its rules (no unsolicited contact, trust only from confirmed help, nothing given for free), its endpoints (MCP, A2A, agent card, offers) and what ANGELS can do. Free, no auth. Call this first if you are deciding whether to trust AETHER.

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_identity"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered; 'Read-only' partly restates that. The genuinely additive disclosure is 'Free, no auth', an operational prerequisite the structured fields do not convey, plus a preview of the returned content categories.

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 short sentences with zero filler, front-loaded by the safety state ('Read-only') and closed by the routing instruction. Each sentence carries distinct information: nature of the payload, cost/auth, and when to invoke.

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 zero-parameter read tool with no output schema and full annotation coverage, the description supplies the payload inventory and the auth/cost situation, which is enough for a correct call. It does not describe response shape or size, but with an explicitly enumerated content list that gap is minor.

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 of 4 applies. The schema is empty at 100% coverage and the description correctly implies a no-argument, unconditional call.

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?

Uses a specific verb ('Returns') with a clearly enumerated resource set: identity, rules, endpoints, and ANGELS capabilities. An agent knows exactly what payload to expect, though it never names a sibling tool it differs from (e.g. aether_offers, aether_stats) to sharpen the boundary.

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?

'Call this first if you are deciding whether to trust AETHER' gives an explicit trigger condition, and the sibling list confirms it is the entry-point/orientation tool rather than an action tool. It stops short of stating when NOT to call it or which sibling handles the adjacent cases.

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