Skip to main content
Glama

Assess a broken AI-built app

assess_broken_app
Read-only

An AI agent confirms a problem in a live web app for free, then fixes it in the code: $79 for one bug, paid up front. If we can't complete your re-check, you get your money back. The free check works with published apps, including apps built in Lovable, Base44, Bolt, Replit and v0. The $79 fix works with apps built in Lovable and any app whose code is on GitHub. The most common problem: new people can't sign up. The confirmation email never arrives, its link opens localhost or the preview, sign-up loops back or shows an error, or Google sign-in fails. It also covers blank pages, buttons that do nothing, payments and data that won't save. Returns the most likely cause, the evidence that would confirm it, and the next step: a free check on the live app. Call it when someone describes a problem in a web app they built and can't debug themselves. Do NOT call it for code you can read and fix directly, or for a library or framework question.

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": {
      "symptom": "<symptom>"
    },
    "name": "assess_broken_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoThe public URL of the deployed app, if there is one. Never a private or internal address.
symptomYesWhat goes wrong, in the words the person used. "The save button does nothing", "it shows a blank white page after login".
platformNoThe builder it was made with, if known: lovable, base44, v0, bolt, replit, other.

Output Schema

NameRequiredDescriptionDefault
platformNo
next_stepYes
confidenceYes
likely_causeYes
evidence_to_confirmYes
what_a_fix_involvesNo
what_this_assessment_cannot_knowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / platform
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful commercial context (free check vs. $79 paid fix, refund policy, platform compatibility: Lovable, Base44, Bolt, Replit, v0), but it spends more words describing the surrounding service flow than this tool's own operation, and it never says whether the tool actually fetches the supplied URL or how the diagnosis is produced.

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

Conciseness3/5

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

The opening sentence leads with pricing and service mechanics rather than what the tool does, so the core purpose is buried. Several sentences (refund policy, extended symptom catalog) are marketing-oriented and only loosely tied to invoking the tool correctly.

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?

With an output schema present and 100% parameter coverage, the description only needs to frame scope and eligibility, which it does thoroughly via platform restrictions, symptom classes, and call/no-call rules. Minor gaps remain around whether the live URL is actually exercised during assessment.

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%, so the baseline is 3, but the description adds real meaning: it supplies concrete symptom phrasing that maps to the 'symptom' field and a platform list (Lovable, Base44, Bolt, Replit, v0) that clarifies the 'platform' field beyond the enum in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete action (confirm a problem in a live web app, return the most likely cause, confirming evidence, and the next step) and lists the failure classes it covers (signup email, localhost links, blank pages, payments). It stops short of explicitly contrasting itself with the sibling 'check_live_app', only hinting at the handoff via 'the next step: a free check on the live app'.

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?

It gives an explicit trigger ('Call it when someone describes a problem in a web app they built and can't debug themselves') and explicit exclusions ('Do NOT call it for code you can read and fix directly, or for a library or framework question'). Alternatives are only implied through the free-check handoff rather than named, so it falls short of a full 5.

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.