Skip to main content
Glama

Get fix guide

get_fix_guide
Read-only

Returns steps to fix a finding type, optionally for a named consent management platform. Cookiebot, CookieYes, OneTrust, Complianz and iubenda have platform-specific steps (in English); for other platforms, or without one, the general steps apply. Includes links to the matching fix guide and knowledge articles on gdprprivacymonitor.eu. Read-only lookup.

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": {
      "finding_type": "<finding_type>"
    },
    "name": "get_fix_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
cmpNoConsent management platform used on the site, for example Cookiebot, CookieYes, Complianz or Borlabs.
languageNoLanguage for explanations and the report link, as an ISO 639-1 code (one of the 24 EU languages). Defaults to en.
finding_typeYesFinding type as reported by get_scan_result, for example pre_consent_tracker or reject_flow_failed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so 'Read-only lookup' is largely redundant. The description does add genuinely useful behavior: five platforms get platform-specific steps in English only, everything else falls back to general steps, and results include links to an external site. It stops short of describing result shape or size, so this is a modest addition rather than a rich one.

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?

Three tight sentences front-load the core behavior, then the platform caveat, then the return contents. The trailing 'Read-only lookup' is the only sentence that fails to earn its place, since the annotations already say it.

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 no output schema, the description carries the burden of describing returns and does so at a high level (fix-guide and knowledge-article links). For a single-required-parameter lookup tool this is essentially complete, with only result structure and volume left unspecified.

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 the baseline is 3. The description does add meaning beyond the schema: it names Cookiebot, CookieYes, OneTrust, Complianz and iubenda as the CMPs with special handling (notably omitting Borlabs, which the schema uses as an example) and implies the language parameter does not change CMP-specific steps since those are English-only.

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: 'Returns steps to fix a finding type,' optionally scoped to a named CMP. The purpose is unmistakably a remediation lookup, distinct from a scan or a general explanation, though it never explicitly says how it differs from the sibling explain_finding.

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?

Implies when to use it by tying finding_type to 'as reported by get_scan_result' in the schema description, and clarifies the CMP-specific vs general fallback. It does not state when to prefer this over explain_finding, and gives no exclusions or prerequisites beyond that.

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