Skip to main content
Glama
Sign In
Italian Data Protection MCP

Italian Data Protection MCP

by Ansvar-Systems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

it_dp_get_guideline

Retrieve a specific Garante guidance document by its database ID for Italian data protection compliance.

Instructions

Get a specific Garante 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": "it_dp_get_guideline"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesGuideline database ID (from it_dp_search_guidelines results)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/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 states only what the tool does, with no information about permissions, error behavior for missing IDs, rate limits, or what the returned document includes, leaving the agent to infer read-only behavior from the verb 'Get'.

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 redundant or filler content. Every word earns its place and conveys the essential operation efficiently.

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?

For a simple one-parameter retrieval tool with full schema coverage and no output schema, the description is minimally adequate. It does not explain the return format or outline when to use it over sibling search tools, but the structured fields cover the invocation mechanics.

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 the single parameter is fully documented as coming from search results. The tool description adds no parameter semantics beyond restating that retrieval is by database ID, so the baseline of 3 is appropriate.

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 states a specific verb ('Get') and resource ('Garante guidance document') with a clear retrieval method ('by its database ID'). It distinguishes itself from search-oriented siblings implicitly by requiring an ID, but it does not explicitly name an alternative or contrast with them, which keeps it from a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no explicit guidance on when to use this tool versus alternatives such as it_dp_search_guidelines. The phrase 'by its database ID' implies a prerequisite, but that is only clarified in the schema parameter description, not in the tool description itself.

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

Deploy Server

Other Tools