Skip to main content
Glama

Privacy

get_privacy
Read-onlyIdempotent

Data processing description, data location, DPO contact and international data transfers (GDPR Chapter V: countries, transfer mechanisms, safeguards).

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": {
      "trust_center": "<trust_center>"
    },
    "name": "get_privacy"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoOptional language code for translated content (bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, it, lt, lv, mt, nl, pl, pt, ro, sk, sl, sv). Defaults to the original language.
trust_centerYesTrust center id (from list_trust_centers), its domain or the exact company name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine scope context by naming GDPR Chapter V specifics (transfer mechanisms, safeguards), which tells the agent what compliance material to expect. It does not state what the response looks like or what happens when a trust center lacks privacy data.

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?

A single compact sentence with the highest-value content (GDPR Chapter V transfers) front-loaded after the core topics. The parenthetical is dense but each listed item is a distinct data area, so little is wasted.

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 two-parameter read tool with full schema coverage, annotations and no output schema, this is close to sufficient. The remaining gap is that the description never frames the call as retrieving one trust center's privacy disclosure, leaving the return shape and the trust_center dependency to the schema.

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%, so both the language enum list and the trust_center identifier rules are already fully documented upstream. The description adds no parameter-level meaning, which is acceptable at this coverage level and yields the baseline score.

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

Purpose3/5

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

The description is a noun-phrase content list ('data processing description, data location, DPO contact and international data transfers') rather than a verb+resource statement, so the action ('get') comes only from the name. It does usefully enumerate the payload's subject matter and implicitly separates it from siblings like get_infrastructure or list_controls, but the phrasing is closer to a label than a purpose statement.

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?

There is no guidance on when to use this instead of siblings such as get_overview or list_subprocessors, and no stated prerequisites. The only actionable detail, needing a trust_center id, lives in the schema rather than the description.

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