Skip to main content
Glama
mahdibrr

dev-error-explainers

by mahdibrr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
explain_errorA

Explain a concrete developer error message or log excerpt and return its documented cause and fix.

Call it when the user pastes (or you captured from a terminal/browser console) an actual error, for example:

  • Node.js ESM/CommonJS errors: ERR_REQUIRE_ESM, ERR_MODULE_NOT_FOUND, "Cannot use import statement outside a module", "require is not defined in ES module scope".

  • npm ERESOLVE / peer-dependency conflict logs from npm install.

  • Next.js next build / next dev output (module not found, heap out of memory, server/client component errors, prerender failures).

  • Browser CORS console errors ("has been blocked by CORS policy", preflight, Access-Control-Allow-Origin).

  • A postgres:// or postgresql:// connection string (DATABASE_URL, Supabase pooler/direct URLs) that fails to connect.

  • Postgres connection errors from Node.js apps: connect ECONNREFUSED / ETIMEDOUT on 5432, getaddrinfo ENOTFOUND, Prisma P1000/P1001/P1017, "password authentication failed", "no pg_hba.conf entry", "too many clients", self-signed certificate. Pass the raw text verbatim, including the stack trace and the "Node.js vX" footer when present; do not paraphrase it.

Returns a short human-readable diagnosis (cause, why, ranked fixes with code, official source links) plus the same result as structured JSON. If nothing is recognised it answers "No known error recognised — nothing guessed"; then rely on your own reasoning.

Fully offline and deterministic: no network, no LLM, same input gives the same output. Secrets it can recognise (URL passwords, Bearer/Basic tokens, JWTs, token/key query parameters) are masked in the output.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.6/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is no possibility of overlap or misselection between tools. Its purpose (diagnose a concrete developer error message) is clearly stated and distinguishable from any generic reasoning the agent might do.

Naming Consistency5/5

The single name explain_error follows a clean verb_noun convention and is self-descriptive. There are no other names to conflict with, so consistency is trivially satisfied.

Tool Count3/5

One tool is borderline thin for a server surface, even though it is well-scoped to a single capability. A single-tool server offers no granularity if callers want, e.g., just the structured or just the lookup.

Completeness4/5

For its narrow stated purpose (explain a pasted error and return cause, fixes, and structured JSON) the surface is self-contained, including an explicit no-match fallback. Coverage is only as broad as its offline known-error database, but no lifecycle operations are obviously missing.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources