Skip to main content
Glama

AI Site Scorer

get_fix_plan

Get the fix plan of a scan: changes ordered by evidence level x ease, stop factors first, each with a ready snippet and a registry card. format: markdown (default), json or prompt (paste into Cursor / Claude Code).

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": {
      "scan_id": "<scan_id>"
    },
    "name": "get_fix_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNomarkdown
scan_idYesScan / job id from scan_site or analyze_url

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: the deterministic ordering rule, the presence of stop factors first, and the per-item shape (snippet + registry card). It does not say whether the plan is computed on demand or cached, how large the output can get, or whether scan_id must reference a completed scan.

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?

Two dense sentences, front-loaded with purpose and followed by format options; nothing is padded. The phrasing "evidence level x ease" is slightly compressed and costs a moment of parsing, the only real deduction.

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?

No output schema exists, so the description must describe returns, and it does so at the right altitude: ordering, item contents, and three output formats. It is sufficient for an agent to call the tool correctly; finer details like size limits or empty-plan behavior are the only gaps.

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 50% because the format enum has no per-value description; the description compensates by explaining that markdown is the default and that "prompt" yields text meant to be pasted into Cursor / Claude Code. scan_id semantics are left to the schema, which already documents its origin.

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 and resource ("Get the fix plan of a scan") and characterizes the payload precisely: changes ordered by evidence level x ease, stop factors first, each with a ready snippet and a registry card. That content signature distinguishes it from report-oriented siblings such as get_report, though no alternative is named outright.

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 implied rather than stated: the description makes clear this is post-scan output and that the prompt format exists for pasting into Cursor / Claude Code, which hints at when to pick each format. There is no explicit when-to-use vs when-not guidance or routing to get_report / generate_fix_prompt.

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