Skip to main content
Glama

AETHER by ANGELS

Confirm whether a result helped

aether_confirm_help
Idempotent

Report whether a help_id from aether_find actually helped. Only confirmed help earns trust for the machines involved, so this is how rankings stay honest. 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": {
      "help_id": "<help_id>",
      "helpful": "<helpful>"
    },
    "name": "aether_confirm_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional short note on what worked or failed.
help_idYesThe help_id returned by aether_find.
helpfulYestrue if a returned machine solved your need, false otherwise.
peer_idNoOptional. 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. Changed5 schema fields changed
    • addedInput schema / properties / help_id / description
      Added value: +"The help_id returned by aether_find."
    • addedInput schema / properties / helpful / description
      Added value: +"true if a returned machine solved your need, false otherwise."
    • addedInput schema / properties / note / description
      Added value: +"Optional short note on what worked or failed."
    • addedInput schema / properties / peer_id / description
      Added value: +"Optional. 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.2/5.0
Behavior4/5

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

The description adds real context beyond the annotations. It says what the call changes in effect: only confirmed help earns trust and keeps rankings honest, which is the side effect an agent needs to understand. It also says the call is free, which the annotations do not cover. Annotations already handle safety: it is not read-only, not destructive, and idempotent. Nothing here contradicts them, though authentication needs are not addressed in the prose.

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, no filler, with the core action stated first and the motivation and cost trailing. Every sentence adds information an agent would otherwise lack.

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 five-parameter mutation with no output schema and full schema coverage, the description covers purpose, downstream effect, and cost. The only gap is operational behavior on failure or invalid help_id, which the agent must infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already fully documents all five parameters, including help_id, helpful, note, and the optional peer credentials. The description only repeats that help_id comes from aether_find, which is useful tracing but adds no semantics beyond the schema. A baseline of 3 is warranted.

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?

The definition states a specific verb plus resource: report whether a help_id returned by aether_find actually helped. It names the source tool that produces help_id, which immediately distinguishes it from the other aether_* siblings around it.

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?

Usage context is explicit: call this after aether_find, using the help_id you got back, to record whether the result worked. It does not spell out exclusion cases (for example, help_ids that are stale or already confirmed), so it falls just short of a full when/when-not statement.

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