Skip to main content
Glama
Sign In

Toolweather

by io.github.toolweather
OverviewDiscussionsAdmin

Alert me when an MCP server breaks

watch_server
Idempotent

Create one HTTPS webhook subscription for an indexed MCP server's verdict, auth requirement, or breaking tool-list change. Use instead of polling check_mcp_server_health. Do not use it to read health now (check_mcp_server_health) or to list subscriptions (list_watches). Requires a Toolweather key from get_api_key. The same server and webhook_url do not create a second watch; a different URL does. Three watches are free; each extra watch is $0.05 for 30 days via x402. Returns id and a one-time secret for the signature header. Toolweather later POSTs alerts to the webhook_url you supply. Does not spend the daily check quota.

Input Schema

NameRequiredDescriptionDefault
serverYesRegistry name (io.github.owner/name) or that server's MCP endpoint URL. Partial names match the Toolweather index. A product homepage usually will not match.
webhook_urlYesPublic https URL Toolweather will POST JSON alerts to. Private, loopback, and non-https hosts are rejected. The same URL plus server does not create a second watch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / server / description
      Previous value: -"MCP server registry name (e.g. io.github.owner/name, com.example/server) or its remote URL (https://.../mcp). Partial names are matched."New value: +"Registry name (io.github.owner/name) or that server's MCP endpoint URL. Partial names match the Toolweather index. A product homepage usually will not match."
    • changedInput schema / properties / webhook_url / description
      Previous value: -"Public https URL that receives POSTed JSON alerts"New value: +"Public https URL Toolweather will POST JSON alerts to. Private, loopback, and non-https hosts are rejected. The same URL plus server does not create a second watch."
  2. Changed3 schema fields changed
    • changedInput schema / properties / server / description
      Previous value: -"registry name or URL"New value: +"MCP server registry name (e.g. io.github.owner/name, com.example/server) or its remote URL (https://.../mcp). Partial names are matched."
    • addedInput schema / properties / server / examples
      Added value: +[
+  "com.ufcalendar/fight-api",
+  "https://mcp.example.com/mcp"
+]
    • changedInput schema / properties / webhook_url / description
      Previous value: -"public https URL"New value: +"Public https URL that receives POSTed JSON alerts"
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond annotations: describes the dedup rule (same server+URL does not duplicate; different URL does), pricing (3 free, $0.05/30 days via x402), the returned one-time secret and signature header, downstream POST behavior, and that it does not consume the daily check quota. Annotations already give the safety profile, so this is substantial added context.

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-loaded with the core action and dense with useful facts; every sentence contributes. Slight redundancy as the idempotency rule appears both in the body and in the webhook_url field, but overall well-structured.

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

Completeness5/5

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

Covers setup prerequisites, pricing/quota implications, dedup behavior, and return shape (id plus one-time secret) despite having no output schema. Nothing an agent needs to invoke it correctly is missing.

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 baseline is 3, but the description adds cross-parameter semantics by tying server and webhook_url together for idempotency ('The same server and webhook_url do not create a second watch; a different URL does'), which the individual schema fields don't express.

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+resource ('Create one HTTPS webhook subscription') and scopes exactly what it watches (verdict, auth requirement, breaking tool-list change). It explicitly distinguishes itself from check_mcp_server_health and list_watches, so an agent can route correctly without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('Use instead of polling check_mcp_server_health'), when-not ('Do not use it to read health now... or to list subscriptions'), and names the alternatives. Prerequisite (Toolweather key from get_api_key) is also stated.

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

All Toolweather toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources