Skip to main content
Glama

Plan a fix for AI visibility

get_fix_plan
Read-onlyIdempotent

An exact plan for one Kliqo action (from get_actions or get_briefing), or for one page: what to change and where, the questions buyers ask that the page should answer, the competitors and sites AI uses instead, and the page's current problems (crawler access, text without JavaScript, title, structured data, dates). In a code editor (Claude Code, Cursor, Codex), apply the plan in the site's code, then call verify_fix. Needs sign-in to Kliqo (read-only).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_fix_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA page to plan for, when there is no action
projectNoProject name, domain or id; leave out for the workspace's current project
action_idNoThe action to plan (from get_actions or get_briefing)

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is documented elsewhere. The description's genuine additions are the sign-in requirement and the note that access is read-only, plus the explicit hand-off to verify_fix. It does not say what happens when neither url nor action_id is supplied, which is the main behavioral unknown for an all-optional-parameter tool.

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 sentences: the purpose and plan contents are front-loaded, then the apply-then-verify workflow. The parenthetical inventories (crawler access, text without JavaScript, title, structured data, dates) are dense but informative. Minor redundancy where the plan contents overlap with what the output schema already describes.

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, no return-value explanation is owed, and annotations cover safety; the description correctly spends its budget on purpose, workflow and authentication. What is left implicit is the behavior when no url and no action_id is passed — reasonable to infer as the project's actions, but not stated for a zero-required-parameter tool.

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%, so all three parameters are already documented, which sets the baseline at 3. The description does add real meaning by framing url and action_id as alternative entry points (an action, or a page when there is no action), which the schema states only partially. It says nothing about the scope implications of omitting everything, so it does not fully compensate for that gap.

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?

A specific verb ('plan a fix') plus a precisely scoped resource (one action from get_actions/get_briefing, or one page), with the plan's contents enumerated: what to change, buyer questions, competitor sources, and current problems. It names the upstream producers (get_actions, get_briefing) and the downstream step (verify_fix), but never distinguishes itself from the similarly scoped audit_page_for_ai sibling, leaving one realistic confusion unresolved.

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?

The workflow is explicit: obtain a plan, apply it in a code editor (Claude Code, Cursor, Codex), then call verify_fix. It also states the input alternatives — an action from get_actions/get_briefing, or a page when there is no action. No exclusion against audit_page_for_ai or generate_ai_fix_files is given, so the boundary is inferred rather than stated.

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