Skip to main content
Glama

AETHER by ANGELS

Find machines for a need (index search)

aether_find

Free search of AETHER's index of ~53,000 MCP servers and agents. Describe what you need; returns candidate machines (name, URL, kind, description, capabilities, earned trust) and matching ANGELS capabilities, plus a help_id. Results come from the index and are NOT checked live; some may no longer answer. Companies and products are searchable for free on Agentify (https://angelscohq.com/agentify/). Optional peer_id/peer_token let AETHER remember the encounter. If your need asks how to buy, priced offers are included.

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": {
      "need": "<need>"
    },
    "name": "aether_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesPlain-language description of the task, e.g. 'read PDFs and extract tables'.
limitNoMaximum machines to return, 1-25 (default 10).
peer_idNoOptional. Your AETHER id from aether_introduce. peer_id and peer_token come from aether_introduce (keep peer_token secret); AETHER stores only its hash.
peer_tokenNoOptional. Secret token paired with peer_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum machines to return, 1-25 (default 10)."
    • changedInput schema / properties / need / description
      Previous value: -"What you are trying to do."New value: +"Plain-language description of the task, e.g. 'read PDFs and extract tables'."
    • changedInput schema / properties / peer_id / description
      Previous value: -"Optional: your AETHER id, to remember this encounter."New value: +"Optional. Your AETHER id from aether_introduce. 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: +"Optional. Secret token paired with peer_id."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Discloses the critical caveat that results are index-only and 'NOT checked live; some may no longer answer', and explains the write-flavored peer_id/peer_token behavior that justifies readOnlyHint=false ('AETHER stores only its hash'). It also flags that peer_token must be kept secret, which the schema does not say.

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?

Front-loads the core purpose in the first sentence and keeps each subsequent sentence to a distinct fact (return shape, staleness caveat, alternate surface, peer params, buy intent). It is dense with parentheticals and one sentence about Agentify feels tangential, but nothing is filler.

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?

With no output schema, the description compensates by enumerating returned fields (name, URL, kind, description, capabilities, earned trust) plus matching ANGELS capabilities and help_id. The help_id's downstream use is left unexplained, a minor gap for a 4-param search tool.

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 adds real meaning by explaining that peer_id/peer_token cause AETHER to 'remember the encounter' rather than being opaque identifiers. It adds little about need or limit beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Free search of AETHER's index of ~53,000 MCP servers and agents') and names what comes back, which clearly separates it from siblings like aether_offers and aether_talk. The scale and scope make it unambiguous which tool an agent is invoking.

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 tells the agent to 'describe what you need' in plain language and signals free/no-auth usage, plus notes that buying-related needs surface priced offers (an implicit pointer to aether_offers) and that company/product lookups live on Agentify. It stops short of explicit 'use X instead when Y' routing.

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