Skip to main content
Glama

Privacyboard vendor guide

Vendor GDPR facts

get_vendor
Read-onlyIdempotent

One tool’s GDPR facts: link to its data processing agreement, usual role (processor or controller), hosting region with source, Data Privacy Framework certification, usual legal bases, what to check and how to declare it.

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": {
      "vendor": "<vendor>"
    },
    "name": "get_vendor"
  }
}

Input Schema

NameRequiredDescriptionDefault
vendorYesTool name, catalog slug or website, such as "Stripe" or "hubspot.com"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds genuine value on the behavioral side by disclosing what the response contains, including provenance for the hosting region ('with source') and actionable elements ('what to check and how to declare it').

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?

One dense sentence, front-loaded with the subject and then the returned facts in a compact list. Every clause is informative; the opening 'One tool's GDPR facts' is slightly awkward phrasing but not wasteful.

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?

With no output schema, the description carries the burden of describing return values, and it enumerates the key returned fields well. Minor gaps remain: unmatched-vendor behavior and whether data is cached or live are unstated, which matters for a compliance 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 coverage is 100% and the single 'vendor' parameter is documented there with examples ('Stripe', 'hubspot.com'). The description adds no meaning beyond the schema, such as how a catalog slug versus a website is resolved or what happens on an unknown vendor, so the baseline of 3 applies.

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 resource and enumerates the exact facts returned (DPA link, processor vs controller role, hosting region with source, DPF certification, legal bases). It is clearly a single-vendor lookup, though it never explicitly contrasts with siblings like search_vendors.

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?

Usage is only implied by the phrase 'One tool's GDPR facts', which suggests a single-vendor detail lookup rather than a search or listing. There is no explicit when-to-use/when-not guidance and no pointer to search_vendors as the alternative for discovering a vendor first.

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