Skip to main content
Glama

AI Site Scorer

generate_fix_prompt

Generate a Cursor/IDE-ready prompt to fix AI readiness issues found in a report. Returns a comprehensive, actionable developer prompt. Pricing: Included with Pro subscription, or $0.002 USDC per request via x402 (no account or free plan).

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": {
      "job_id": "<job_id>"
    },
    "name": "generate_fix_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYesThe UUID job_id of a completed report.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses billing behavior (Pro subscription or $0.002 USDC per request via x402, no free plan), which is real behavioral context an agent needs before repeated calls. It omits whether the operation is read-only/idempotent, whether it errors on an unknown or incomplete job_id, and any rate or length limits on the generated prompt.

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?

Purpose is front-loaded in the first sentence, with the return value and pricing following in descending order of importance. The pricing sentence is long relative to its value but does carry information an agent cannot get elsewhere.

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

Completeness3/5

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

For a one-parameter, no-output-schema tool the description is mostly sufficient: it says what comes back and what it costs. The notable gap is sibling disambiguation from get_fix_plan and the absence of any failure-mode note, which matters for a tool charged per request.

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?

The single parameter is fully documented in the schema (100% coverage, UUID of a completed report), so the schema does the work and baseline 3 applies. The description adds only the framing that the issues come "from a report," which is already implied by job_id.

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?

States a specific verb+resource+output shape: "Generate a Cursor/IDE-ready prompt to fix AI readiness issues found in a report." An agent can tell this produces a developer prompt rather than raw analysis. It does not, however, distinguish itself from the sibling get_fix_plan, which an agent could reasonably confuse with this tool.

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

Usage Guidelines3/5

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

Usage is only implied: the schema requires a job_id "of a completed report," which tells the agent this runs after a report exists. There is no explicit when-to-use guidance, no statement of when to prefer get_fix_plan or enhance_report instead, and no mention of what happens if the report is incomplete.

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