Skip to main content
Glama

Explain a finding

explain_finding
Read-only

Explains a GDPR Privacy Monitor finding type, such as pre_consent_tracker or reject_flow_failed: what was detected, why it matters, and suggested wording for explaining it to the site owner, in the requested language. Looks the type up in a fixed catalogue; it does not scan anything. Technical explanation, not legal advice.

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": "explain_finding"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), and the description adds real context beyond them: the lookup is against a fixed catalogue, it performs no scanning, and the output is a technical explanation rather than legal advice. That last caveat is a meaningful disclosure about what the agent can and cannot claim from the result.

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-loaded with the action and the resource before the scope caveats. Nothing is filler, though the phrase 'suggested wording for explaining it to the site owner' is slightly more verbose than needed to convey the return content.

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?

For a simple two-parameter read-only lookup with no output schema, the description is nearly sufficient: it names the inputs, the source of truth (a fixed catalogue), and the shape of the answer. It does not state what happens when an unrecognized finding_type is passed, which is the one gap for a catalogue-backed lookup.

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 description coverage is 100% and both the finding_type examples and the full 24-language enum with its default are already in the schema. The description only restates 'in the requested language' and reuses the same two example finding types, adding no syntax or constraint detail beyond the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb (explains) plus a named resource (a GDPR Privacy Monitor finding type), with concrete examples (pre_consent_tracker, reject_flow_failed) and a clear statement of what the output contains. The line 'Looks the type up in a fixed catalogue; it does not scan anything' cleanly separates it from scan_website and get_scan_result.

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 description implies the workflow by saying finding_type is the value 'reported by get_scan_result', and it rules out the wrong use case by stating it does not scan anything. It does not explicitly name get_fix_guide as the alternative for remediation versus explanation, so it stops short of full routing guidance.

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