Skip to main content
Glama
Sign In
MCP Error Relay

MCP Error Relay

by purelledhand
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_server_list

Read-onlyIdempotent

Get a list of MCP servers with error counts and recent activity to quickly identify which server logs to inspect when a tool fails.

Instructions

List Available MCP Servers

Use this tool FIRST if you don't know which MCP server name to use for error checking.

WHEN TO USE:

  • A tool failed but you don't know the exact server_name

  • You want to see which servers have recent errors

  • You're not sure if logs exist for a particular server

  • You need to identify which servers are most problematic

WHAT THIS TOOL SHOWS: ✅ All available MCP server names (needed for other tools) ✅ Total error counts per server ✅ Recent errors in last 24 hours ✅ When logs were last updated ✅ Full log file paths

WORKFLOW:

  1. Tool fails, but you're unsure of the server_name

  2. Call THIS tool to list all available servers

  3. Find the server with recent errors or matching your failed tool

  4. Use that server_name to call get_recent_errors

USE CASES:

  • Error says "slack tool failed" -> List servers -> Find "slack-mcp-server" -> Check its logs

  • Multiple tools failing -> List servers -> See which has most errors (24h column) -> Investigate that one first

  • New to the system -> List servers -> Understand available MCP infrastructure

TIP: Look at the "recent_error_count" (last 24h) to identify servers currently having problems!

Args:

  • include_stats (boolean): Include error statistics for each server (default: true)

  • response_format ('markdown' | 'json'): Output format (default: 'markdown')

Returns: For Markdown format: Human-readable list with server names and stats For JSON format: Structured data with schema: { "total": number, // Number of servers found "servers": [ { "server_name": string, // Name of the MCP server "log_file_path": string, // Full path to log file "last_modified": string, // ISO 8601 timestamp of last update "total_errors": number, // Total error count (if include_stats=true) "recent_error_count": number // Errors in last 24h (if include_stats=true) } ] }

Examples:

  • Don't know server name -> {}

  • Quick server list -> { include_stats: false }

  • Find problematic server -> {} (then check recent_error_count)

Error Handling:

  • Returns empty list if no log files found in configured directory

  • Gracefully handles log files with different formats

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_server_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_statsNoWhether to include error statistics for each server (default: true)
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is known. The description adds behavioral context beyond annotations: returns an empty list when no logs exist, gracefully handles varied log formats, and defines the exact output structure for both markdown and JSON responses.

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 description is long but well-organized with sections (WHEN TO USE, WHAT THIS TOOL SHOWS, WORKFLOW, USE CASES, Returns, Examples, Error Handling). The primary purpose is front-loaded in the first line. Minor redundancy exists (the 'use first' guidance appears twice), but overall structure makes the length acceptable.

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 thoroughly explains return values, including a JSON schema for both markdown and json formats, examples, and error handling (empty list, malformed log files). Combined with the annotations and parameter descriptions, an agent has all necessary information to select and invoke this tool correctly.

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?

The schema covers 100% of parameters with descriptions, giving a baseline of 3. The description goes further by explaining how 'include_stats' conditionally includes fields (total_errors, recent_error_count) and providing examples of parameter usage, adding practical meaning beyond the schema text.

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?

The description opens with 'List Available MCP Servers', a specific verb+resource phrase, and expands on exactly what is listed (server names, error counts, recent errors, log paths). It clearly distinguishes itself from siblings by positioning this as the first step before invoking get_recent_errors or get_error_details.

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?

The 'WHEN TO USE' section provides concrete scenarios (e.g., 'tool failed but you don't know the exact server_name') and an explicit workflow that names the sibling tool get_recent_errors as the next step. This offers clear guidance on when this tool should be used over alternatives.

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