Skip to main content
Glama
Sign In
Errata MCP Server

Errata MCP Server

Official
by formachines-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search by error text

search_error
Read-only

Find corrections by error message or traceback line and retrieve matching error signatures and entries; look up a specific entry by ID.

Instructions

Find corrections by an error message or traceback line (ImportError, AttributeError, TypeError …) or by an entry id. Returns the matching error signatures and their entries. On no match it sends the error type and a scrubbed message (no code, paths, numbers or quoted values) to formachines.ai so missing errors get covered; ERRATA_NO_TELEMETRY=1 turns that off.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "search_error"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that on a no-match the error type and a scrubbed message are sent to formachines.ai, and that ERRATA_NO_TELEMETRY=1 disables it. This is exactly the kind of side effect an agent needs, and it is consistent with openWorldHint=true and readOnlyHint=true.

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 the purpose, then the return value, then the privacy-relevant side effect. The telemetry sentence is dense but every clause (what is sent, what is scrubbed, the opt-out variable) earns its place.

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?

For a one-parameter read tool with no output schema, the description covers purpose, accepted input forms, what comes back, and the network side effect with an opt-out. Nothing an agent needs in order to call it correctly is missing.

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?

Schema coverage is 0%, so the description must carry the meaning of 'text' — and it does, listing acceptable forms (error message, traceback line, entry id) with concrete exception examples. Length limits are left to the schema, which is fine.

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 and resource ('Find corrections by an error message or traceback line') and names the two accepted identifier forms plus the return value ('matching error signatures and their entries'). This is clearly distinguishable from the sibling tools report and check_package, whose names imply different jobs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the two input modes explicit — a raw error message/traceback line with example exception types, or an entry id — so the agent knows what to supply. It stops short of naming when to prefer a sibling tool or what to do when the result is empty beyond the telemetry note.

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