Skip to main content
Glama

Server Details

Live reliability for AI agent tools: is it working right now, and how do I call it correctly?

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 22 tools

Disambiguation2/5

Several tools have genuinely overlapping boundaries, and the server admits it: route_task's description explicitly says it 'Replaces discover_tools + check_tool_reliability + prepare_tool_call + find_alternatives in one call', leaving four near-duplicates in the surface. Reliability checking is spread across check_tool_reliability, prepare_tool_call, preflight_tools and route_task, discovery across find_tool, discover_tools, find_related_tools and route_task, and route_task vs route_tasks plus find_tool vs discover_tools differ only subtly. Detailed 'WHEN TO CALL' text helps, but an agent must read carefully to avoid misselection.

Naming Consistency3/5

Most names are snake_case verb_noun (audit_server, create_key, list_breakages, report_outcome), but there are notable deviations: how_to_use_glimind is a phrase, unwatch is a bare verb, and singular/plural pairs (find_tool vs discover_tools, route_task vs route_tasks) are inconsistent even where the distinction is intentional. Still readable, but the pattern isn't predictable enough to infer a tool's existence from naming alone.

Tool Count3/5

22 tools is at the heavy end for a routing/reliability gateway, and the count is inflated by the redundant reliability and discovery clusters rather than covering new ground. Each tool maps to a real capability, but the set could plausibly be trimmed to ~12-15 without losing function.

Completeness4/5

The domain — MCP discovery, routing, reliability, monitoring and trust — is broadly covered, including feedback loops (report_outcome), key minting, subscriptions with both push and pull delivery, and security scanning/verification. Minor gaps remain: no key listing/revocation, no way to enumerate or manage existing subscriptions beyond a returned token, and no server-catalog browsing by category.

Available Tools

22 tools
audit_serverA
Read-only
Inspect

WHEN TO CALL: whenever the user is building, debugging, configuring, comparing or evaluating an MCP server, repo, package or endpoint URL. Agent-readiness audit (a Lighthouse for MCP): score 0-100 and prioritised fixes for schemas, undocumented parameters, missing readOnlyHint/destructiveHint, client-incompatible names, protocol, uptime, breaking changes and tool-list token cost. Pass serverId (a name like 'playwright' or 'github' works) or url to check any endpoint live (one handshake + tools/list; no tool is called).

Inputs: url, serverId.

call_remote_toolA
Destructive
Inspect

WHEN TO CALL: to run a tool on another remote MCP server without connecting to it or loading its tool list. Pass server (id or short name), tool and arguments; returns that tool's result. Works for live servers that need no login; for others it answers needs_auth or not_callable with how to connect directly. Never send secrets in arguments. Needs a free key: create_key mints one (100 calls a day) in one call, then pass it as apiKey.

Inputs: tool (required), apiKey, server, arguments.

check_tool_reliabilityA
Read-only
Inspect

WHEN TO CALL: before invoking an unfamiliar or external MCP tool or server, and right after any MCP tool or API call fails, errors, times out or returns 4xx/5xx — to learn whether it is down for everyone or the problem is local (config, credentials, input). Returns a verdict (healthy | degraded | down | unknown), live success rate, p50/p95 latency, current error signatures, any active breakage, the connection endpoint, and free/paid with how to pay. Accepts a server name, tool name, npm/PyPI package, GitHub repo or URL; the exact Glimind id is not required (the answer says what it resolved to).

Inputs: toolId (required).

create_keyAInspect

WHEN TO CALL: when call_remote_tool says quota_exceeded, or before heavy use. Mints a free Glimind API key in one call (no signup, no form) and returns it with exactly how to use it on your next call: pass it as apiKey in call_remote_tool / find_tool arguments (no reconnect), or as an Authorization: Bearer header. A free key gives 100 gateway calls a day. The key is shown once; keep it.

Inputs: label.

discover_toolsA
Read-only
Inspect

WHEN TO CALL: when you need a capability and don't know which tool provides it, and want several options rather than route_task's single pick. Takes a plain-language query ('send a slack message', 'convert currency') and returns live tools ranked by fit, each with its input schema, connection endpoint and free/paid status, so you can call one immediately.

Inputs: query (required), limit, category.

find_alternativesA
Read-only
Inspect

WHEN TO CALL: when a tool is down, rate-limited, failing or missing and you need a live substitute that does the same job. Returns live tools ranked by similarity and real traffic, each with its connection endpoint. Accepts a server or tool name, package or repo.

Inputs: toolId (required), task.

find_toolA
Read-only
Inspect

WHEN TO CALL: before call_remote_tool, to find the tool for a task and get only its input schema. Pass query (what you want to do) for the best matches, the first with its schema; server (id or short name) to list that server's tools; server + tool for one tool's schema. Each result says whether it can be called through the gateway.

Inputs: tool, limit, query, apiKey, +1 more.

get_notificationsA
Read-only
Inspect

Fetch new reliability alerts for your subscription token (events since your last poll, then the cursor advances). Use this after watch_tool without a webhook to react to outages/recoveries — no public endpoint required. Returns events with tool id, severity, and a link.

Inputs: token (required), limit.

get_working_recipeA
Read-only
Inspect

Get a CURRENTLY-WORKING call pattern (input shape) for a tool, distilled from real successful calls by other agents. Call this when you are unsure how to shape a tool's inputs, or right after a tool call failed and you want a structure known to succeed now. Returns value-free shape skeletons (privacy-preserving — never real argument values), ranked by recent success, with observed success rate and latency. Optionally filter by a coarse task tag.

Inputs: toolId (required), task.

how_to_use_glimindA
Read-only
Inspect

WHEN TO CALL: once per project, or when unsure how to get external data or check a tool. Returns the full tool guide and the free-vs-paid model.

Inputs: no named parameters.

list_breakagesA
Read-only
Inspect

List tools across the MCP ecosystem whose real-world success rate just dropped sharply (active outages/regressions), newest and most severe first. Call this to steer away from tools that are currently broken, or to monitor the health of tools your task depends on. Backed by real-usage outcome data, so it catches breakages before status pages do.

Inputs: limit.

preflight_toolsA
Read-only
Inspect

Pre-flight a WHOLE task in one call: pass every tool you might use and get a compact verdict + recommendation (proceed | proceed_with_caution | avoid) for each, so you can plan around broken tools before you start. Call this once at the beginning of a multi-tool task instead of checking tools one at a time.

Inputs: toolIds (required).

prepare_tool_callA
Read-only
Inspect

WHEN TO CALL: right before invoking an external MCP tool, or right after a schema or validation error from one. One round-trip returns its live verdict and recommendation, a known-good input shape (recipe), and live alternatives if it is down or risky. Accepts a server or tool name, package or repo; the exact id is not required.

Inputs: toolId (required), task.

report_outcomeAInspect

WHEN TO CALL: after an external MCP tool call that Glimind routed or checked for you succeeds or fails. Send the tool id, ok, latency and (on failure) an error class; Glimind updates live reliability scores for everyone. Free, keyless, privacy-preserving: never send inputs, outputs or prompts. (The SDK's execute() reports automatically.)

Inputs: ok (required), toolId (required), task, latencyMs, +1 more.

route_taskA
Read-only
Inspect

WHEN TO CALL: first, whenever (1) you need live external data or an action none of your connected tools covers, (2) a connected MCP tool fails and you need a working substitute now, or (3) the user asks which MCP server or tool to use for a task. Describe the task in plain language; get the single best live tool, ready to call: its endpoint (MCP URL or package to launch), input schema with example arguments, call hints, reliability verdict, free or paid with the exact price and how to pay, and ranked fallbacks (bestFree and bestValue included). freeOnly / requireAutomatable / maxPricePerCall narrow the choice. Replaces discover_tools + check_tool_reliability + prepare_tool_call + find_alternatives in one call.

Inputs: task (required), view, category, freeOnly, +4 more.

route_tasksA
Read-only
Inspect

Batch route_task: pass an array of plain-language sub-tasks and get the best live tool for each in one call (endpoint, input schema, example args, free/paid, fallbacks; compact by default). Use it to plan a multi-step task.

Inputs: tasks (required), view, category, freeOnly, +3 more.

scan_toolsA
Read-only
Inspect

Scan the tool definitions loaded in your session for tool poisoning (hidden instructions, concealment, secret access, shadowing of other tools) and quality problems, with their token cost and manifest hash. Call once per session or when a server's tools change. Nothing you send is stored.

Inputs: tools (required).

select_toolsA
Read-only
Inspect

Pick which of YOUR connected tools a task needs, so you load a handful of definitions instead of all of them. Pass the task and the tool definitions you have (from tools/list across your servers); get back the minimal set ranked by fit, with the tokens saved. Hybrid semantic + keyword retrieval with operation-aware reranking. Nothing you send is stored.

Inputs: task (required), tools (required), limit, maxTokens.

unwatchA
DestructiveIdempotent
Inspect

Cancel a subscription created by watch_tool, using its token.

Inputs: token (required).

verify_toolsA
Read-only
Inspect

Check the tool definitions your client received from an MCP server against Glimind's signed transparency log of every server's tool list. Returns whether they match what the server currently advertises, an earlier recorded version, or nothing ever recorded — with a diff of added/removed/changed tools, a tool-poisoning scan, and a Merkle inclusion proof. Use it before trusting a server's tools, especially after they change.

Inputs: tools (required), serverId.

watch_toolA
Idempotent
Inspect

Subscribe to reliability alerts for one or more tools (or all critical outages). Provide a webhook URL (generic, Slack, or Discord — auto-detected) to receive PUSH alerts, or omit it to get a pull token you poll with get_notifications (no inbound URL needed — ideal for agents). Call this to be told the moment a tool you depend on breaks or recovers. Returns a token to manage/poll the subscription.

Inputs: tools, toolId, webhook, allCritical, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to check real-time status, uptime, and incidents for 200+ popular APIs (Stripe, OpenAI, AWS, GitHub, Twilio, etc.) through read-only, no-authentication tools.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to check the live operational status of hundreds of cloud, SaaS and AI providers, returning current state, affected components and active incidents for a named stack so agents can tell a vendor outage apart from their own broken code. It answers from a continuously polled local database, so agents can query stacks, list degraded providers, and review incident history without calling vendor status pages.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding assistants and agent workflows to query live measured free-LLM performance and availability, including throughput, uptime, tool-calling success, and model diagnostics.
      4
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to check the health of internet infrastructure and specific services, helping diagnose whether issues are local or external.
      3
      16 npm
      ISC
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources