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.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 25). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions being backed by real-usage outcome data and catching breakages early, implying a read-only query. However, it doesn't explicitly state safety or non-destructive nature, leaving room for ambiguity.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences with no redundancy. It front-loads the purpose and provides usage rationale efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description should hint at return format but does not. It mentions listing tools but omits what fields are returned. However, for a simple list tool, it is partially adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% for the single 'limit' parameter. The tool description does not add additional meaning beyond the schema's parameter description, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists tools with dropped success rates (breakages), ordered by newest and most severe. It distinguishes from siblings like 'check_tool_reliability' by focusing on breakages from real-usage data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly says 'Call this to steer away from tools that are currently broken, or to monitor the health of tools your task depends on.' This provides clear context for when to use, though it lacks mention of when not to use or explicit alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a distinct, well-defined purpose: checking reliability, discovering tools, finding alternatives, getting recipes, routing tasks, etc. No two tools overlap in function.
All tool names follow a consistent verb_noun pattern with underscores (e.g., check_tool_reliability, route_task, watch_tool). The only minor deviation is 'how_to_use_glimind', which still follows a clear verb phrase convention.
With 15 tools, the set is well-scoped for a comprehensive meta-layer covering discovery, reliability checking, preparation, batch routing, reporting, and notifications. Each tool earns its place.
The surface covers the full workflow of discovering, checking, preparing, calling, and reporting on tools. A minor gap is the lack of a direct 'list all tools' catalog, but the discovery tools effectively fill this need.