VibeFix

Get the options for fixing an app

get_fix_options

Read-only

Returns the link to a sign-up check of a live app on vibe-fixer.com. An AI agent signs up as a brand-new person with a real inbox, on a phone and a computer, and reports whether a new person can finish signing up, plus anything else a first customer would hit. It also says how the fix works and what the person provides. Read-only: it starts nothing, charges nothing and does not contact the app. Call it when the person wants their live app checked or fixed, for example after assess_broken_app.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No	The public URL of the deployed app, if known. Never a private or internal address.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`limits`	Yes
`test_link`	Yes
`how_it_works`	Yes
`what_the_person_provides`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 6, 2026

removedOutput schema / properties / pricing_info
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / required

Previous value: -[
-  "test_link",
-  "how_it_works",
-  "pricing_info",
-  "what_the_person_provides",
-  "limits"
-]New value: +[
+  "test_link",
+  "how_it_works",
+  "what_the_person_provides",
+  "limits"
+]

Changed3 schema fields changedOct 4, 2026

removedOutput schema / properties / plans

Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "billing": {
-        "enum": [
-          "monthly",
-          "one-time"
-        ],
-        "type": "string"
-      },
-      "credits": {
-        "type": "number"
-      },
-      "name": {
-        "type": "string"
-      },
-      "price_usd": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "name",
-      "price_usd",
-      "billing",
-      "credits"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedOutput schema / properties / pricing_info
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "test_link",
-  "how_it_works",
-  "plans",
-  "what_the_person_provides",
-  "limits"
-]New value: +[
+  "test_link",
+  "how_it_works",
+  "pricing_info",
+  "what_the_person_provides",
+  "limits"
+]

AddedSep 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false; the description reinforces this and adds real value by stating it "starts nothing, charges nothing and does not contact the app", which addresses cost and side-effect concerns an agent would otherwise have to guess at. It stays consistent with the annotations rather than contradicting them.

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 deliverable and the read-only constraint are front-loaded, and the usage trigger lands in the final sentence. The middle sentence describing the simulated sign-up is wordy, but each sentence does carry information that helps selection.

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?

An output schema exists, so return values need no explanation, and the description covers what the tool does, what it costs and when to call it. The remaining gap is the relationship and sequencing with assess_broken_app, which is only hinted at by "for example after".

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single url parameter is fully documented in the schema, including the public/private-address restriction. The description only refers to "a live app" generically and adds no format or sourcing guidance beyond the schema, so the baseline 3 applies.

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 states a concrete deliverable (a link to a sign-up check on vibe-fixer.com) and spells out what that check covers, which explains the otherwise opaque name 'get_fix_options'. It names the sibling assess_broken_app as the natural predecessor, giving an agent enough to separate the two, though the split of labor between them is only implied.

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?

"Call it when the person wants their live app checked or fixed, for example after assess_broken_app" gives an explicit trigger condition and positions the tool after its sibling. No when-not-to-use or unsupported-case guidance is offered, so it stops short of a 5.

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

All VibeFix tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.