estonian-data-protection-mcp

ee_dp_get_guideline

Retrieve a specific AKI guidance document by its database ID to access official Estonian data protection guidelines.

Instructions

Get a specific AKI guidance document by its database ID.

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": {
      "id": "<id>"
    },
    "name": "ee_dp_get_guideline"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Guideline database ID (from ee_dp_search_guidelines results)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 10, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a retrieval operation ('Get') but does not disclose the return format, whether it returns the full document or metadata, or error behavior for invalid IDs. It adds minimal context beyond the action itself.

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?

The description is a single, front-loaded sentence with no unnecessary words. It accurately and efficiently communicates the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one parameter and no output schema, so the description should at least indicate what the response will contain. 'Guidance document' is vague about structure or content. However, for a straightforward get-by-ID tool, it provides enough to select the tool, though not enough to predict the full response shape.

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?

The input schema covers 100% of parameters, with the 'id' field described as 'Guideline database ID (from ee_dp_search_guidelines results)'. This gives clear provenance for the parameter. The tool description adds no further detail, so baseline 3 applies.

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?

The description clearly states the tool's function: 'Get a specific AKI guidance document by its database ID.' It uses a specific verb ('Get'), identifies the resource ('AKI guidance document'), and specifies the key parameter ('database ID'). This distinguishes it from sibling tools like ee_dp_search_guidelines, which is for searching.

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 usage context by specifying 'by its database ID' and the parameter description clarifies that the ID comes from ee_dp_search_guidelines results. This effectively tells the agent when to use this tool (after a search) without explicitly naming alternatives. It's clear but doesn't state exclusions or conditions.

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

Deploy Server