Skip to main content
Glama
Sign In

Toolweather

by io.github.toolweather
OverviewDiscussionsAdmin

Is this MCP server healthy / safe to call right now?

check_mcp_server_health
Read-onlyIdempotent

Read whether one remote MCP server, and optionally one tool on it, is safe to call right now. Use before adding or calling that server, or after its calls fail or time out. Do not use it to search by capability (find_alternative_mcp_servers), to vet a list (batch_check_mcp_servers; stored verdicts only), or to subscribe to later outages (watch_server). A result older than 5 minutes, or fresh/bearer_token, runs one read-only initialize and spends a live-check credit (200/day, then the cache). Counts on the Toolweather quota (1,000/key or 50/day anonymous). Returns summary, verdict (safe|caution|unsafe|unknown), recommended_action (call_it|call_with_care|use_alternative|verify_yourself), reasons, latency_ms, auth, last_tool_change, checked_at, and freshness. Also callable as is_safe_to_call.

Input Schema

NameRequiredDescriptionDefault
toolNoOptional tool name on that server. If the server is up but this name is absent, verdict is unsafe. Omit to judge the server only.
freshNoTrue forces a live read-only initialize now and spends one of 200 live checks/day (priced as a live check). Omit to live-check only when the stored result is older than 5 minutes.
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.
bearer_tokenNoToken for the target server only, not a Toolweather key. One authenticated initialize + tools/list, never stored or logged. Setting it forces a live check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / bearer_token / description
      Previous value: -"Optional: your own token for this server, for a one-off authenticated initialize + tools/list check. Used once, never stored or logged."New value: +"Token for the target server only, not a Toolweather key. One authenticated initialize + tools/list, never stored or logged. Setting it forces a live check."
    • changedInput schema / properties / fresh / description
      Previous value: -"Force a live handshake now (otherwise automatic when the stored check is >5 min old)"New value: +"True forces a live read-only initialize now and spends one of 200 live checks/day (priced as a live check). Omit to live-check only when the stored result is older than 5 minutes."
    • 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 / tool / description
      Previous value: -"Optional tool name to confirm it still exists on the server, e.g. search"New value: +"Optional tool name on that server. If the server is up but this name is absent, verdict is unsafe. Omit to judge the server only."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds behavior annotations don't cover: the 5-minute cache threshold, that stale/fresh/bearer_token triggers a live read-only initialize, the 200/day live-check budget falling back to cache, and the Toolweather quota (1,000/key or 50/day anon). This is unusually rich quota, caching, and auth-handling disclosure.

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 purpose, then usage, exclusions, behavior, and returns; every sentence carries information. The enumerated return fields and alias mention border on density, but since there is no output schema they are justified rather than wasteful.

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?

With no output schema, the description compensates by listing the full return surface (verdict, recommended_action, reasons, latency_ms, auth, last_tool_change, checked_at, freshness). Combined with quota/caching notes and the sibling routing, an agent has everything needed to call and interpret this tool correctly.

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%, so the schema already documents all four parameters (including tool, fresh, server matching rules, and bearer_token scope). The description restates the fresh/bearer_token live-check behavior but adds no parameter detail the schema lacks, so the baseline 3 applies.

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 (read) and resource (one remote MCP server, optionally one tool) plus the exact scope: 'safe to call right now.' It explicitly distinguishes itself from siblings (find_alternative_mcp_servers, batch_check_mcp_servers, watch_server), so an agent can differentiate without opening any schema.

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 trigger conditions ('before adding or calling that server, or after its calls fail or time out') and explicit exclusions naming the correct alternative for each ('Do not use it to search by capability... to vet a list... or to subscribe to later outages'). Nothing is left to inference.

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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources