Skip to main content
Glama

get_checklist

Retrieves required privacy-policy sections for configured KR and GDPR jurisdictions, the legal basis for each section, default change-notice periods, and the response format to use.

Instructions

Call to get the required sections a privacy policy must have for the configured jurisdictions (kr, gdpr), the legal basis for each, default notice periods for changes, and the answer format to use.

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_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden, and it only confirms that the result is derived from 'configured' jurisdictions rather than request input. It says nothing about whether the operation is read-only (implied but unstated), what happens if no jurisdictions are configured, or how errors surface.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. The enumerated payload items are all load-bearing because, with no output schema, they are the only signal of what comes back.

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 parameterless read tool with no annotations and no output schema, the description covers the essential return contents (sections, legal basis, notice periods, answer format). Minor gaps remain around the concrete shape of the response and behavior when configuration is missing.

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?

The tool takes zero parameters, which sets a baseline of 4. The description earns that baseline by clarifying that jurisdictions (kr, gdpr) come from configuration rather than being selectable per call, which prevents the agent from hunting for a jurisdiction argument that does not exist.

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?

The description names a specific verb and resource and then enumerates exactly what the returned checklist contains (required sections, legal basis per section, default notice periods, answer format). That makes its purpose distinguishable from a generic policy getter, though it never names a sibling tool to contrast with.

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?

There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance. The framing 'Call to get...' and the mention of 'the answer format to use' imply this is a setup step before authoring or validating a policy, but the agent must infer that sequencing itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.