Skip to main content
Glama
Sign In
astroway-mcp

astroway-mcp

Official
by astroway
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Register Retrograde-End Webhook

astroway_webhooks_retrograde_end

Register a webhook URL to be notified when any Mercury–Pluto planet stations direct, enabling timely retrograde-end updates.

Instructions

Fires when any of Mercury–Pluto stations direct.

[Group: Webhooks] [Endpoint: POST /v1/webhooks/retrograde-end] [Required: url] [Cost: 10 credits (Tier 1)]

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": {
      "url": "<url>"
    },
    "name": "astroway_webhooks_retrograde_end"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Output Schema

NameRequiredDescriptionDefault
idNo
eventNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly, non-idempotent, open-world mutation, and the description adds useful context: the exact trigger condition (Mercury through Pluto stationing direct) and the 10-credit Tier 1 cost. It does not disclose delivery semantics, whether duplicate registrations are allowed (consistent with idempotentHint=false), auth requirements, or how to later remove the webhook.

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?

The bracketed metadata lines are compact and the trigger condition is front-loaded, so there is minimal waste. The structure is terse but scannable, though the lead sentence could be rewritten to name the action first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and cost/endpoint/required URL are covered. However, for a webhook-registration mutation the description omits key context: whether one registration covers all six planets or fires per planet, auth, duplicate handling, and the unsubscribe/lifecycle path.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must explain the single `url` parameter, but it only restates '[Required: url]' which the schema already enforces. It adds no meaning about whether the URL must be HTTPS, publicly reachable, or what happens if it fails validation.

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

Purpose3/5

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

The description's lead sentence, 'Fires when any of Mercury–Pluto stations direct,' describes the triggering event rather than the tool's action, so an agent must infer from the title and '[Endpoint: POST /v1/webhooks/retrograde-end]' that this registers a webhook. It never explicitly says 'register a callback URL,' and the nearby inverse sibling astroway_webhooks_retrograde_start is never referenced.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this registration versus astroway_webhooks_retrograde_start, astroway_webhooks_subscribe, or the generic webhooks manager. Nothing states prerequisites, that a URL is the callback target, or when a caller should prefer this event over the broader transit trigger.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools