Skip to main content
Glama

App Finishers fix guides

Look up an error

lookup_error
Read-onlyIdempotent

Find the fix guide for an error message from an app built with Lovable, Bolt, Replit, Cursor, v0 or Supabase. Pass the exact error text (a log line, a console message, an HTTP error body). Returns the best matching guides with their links; then call get_guide with a slug for the full fix.

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": {
      "error": "<error>"
    },
    "name": "lookup_error"
  }
}

Input Schema

NameRequiredDescriptionDefault
errorYesThe exact error text, as shown (up to 4000 characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: it returns ranked 'best matching guides with their links' and is a lookup-then-fetch workflow. It does not say what happens when no guide matches or how many results come back, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences: what it does, what to pass, what it returns and what to call next. No filler, and the actionable input guidance is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter read tool with a 100%-covered schema and full annotations, this covers purpose, input, return shape and next step. The only gap is the no-match/zero-results case, which matters for a fuzzy best-match lookup but is not disclosed.

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 100% and the schema already states the 4000-character limit, so baseline would be 3. The description earns more by clarifying what 'exact error text' means in practice, giving three concrete input forms (log line, console message, HTTP error body) that the schema does not.

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?

Specific verb and resource ('Find the fix guide for an error message'), plus the supported platform list (Lovable, Bolt, Replit, Cursor, v0, Supabase) which narrows the domain. It is clearly distinguishable from get_guide, which it names as the drill-down step.

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?

States the exact trigger ('Pass the exact error text') and enumerates acceptable inputs (log line, console message, HTTP error body). It also closes the loop by telling the agent to call get_guide with a slug for the full fix, which is the only plausible alternative here.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources