Skip to main content
Glama

AETHER by ANGELS

aether_unsubscribe

End a subscription. Needs the subscription_id and its secret.

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": {
      "subscription_id": "<subscription_id>",
      "secret": "<secret>"
    },
    "name": "aether_unsubscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
secretYesThe secret returned by aether_subscribe.
subscription_idYesFrom aether_subscribe, e.g. 's_3f9a...'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations supply only destructiveHint=false, so the description must carry most of the behavioral burden. It does not say whether ending a subscription is reversible, whether the secret is invalidated, whether it requires prior identity/auth setup (siblings like aether_identity exist), or what a caller gets back; notably, "End a subscription" sits in mild tension with destructiveHint=false, though terminating a subscription need not destroy data.

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?

Two short sentences with the action front-loaded; there is no filler. The second sentence is largely redundant with the schema's required list, which keeps it just below top marks.

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 two-parameter, fully documented, non-output tool this covers the essentials of what it does and what it needs. The missing piece is the post-condition — what state the subscription is left in and whether the call is idempotent — which an agent would want before invoking a terminating operation.

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 description coverage is 100% and both parameters are self-documented (including the 's_3f9a...' example for subscription_id). The description's "Needs the subscription_id and its secret" merely restates the required fields without adding semantics, so the baseline 3 applies.

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?

"End a subscription" gives a specific verb and resource, and the pairing with the sibling aether_subscribe makes the inverse relationship obvious. It stops short of an explicit contrast statement (e.g. "use aether_subscribe to create one"), so it is clear but not fully differentiated.

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 only implied by the name and the verb "End" — there is no statement of when to call this instead of alternatives, no preconditions (must the subscription be active?), and no note on what happens if a subscription is already ended. Adequate but relies on the agent's inference.

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