Skip to main content
Glama

Subprocessors

list_subprocessors
Read-onlyIdempotent

Subprocessors with purpose, location and transfer mechanism.

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": "list_subprocessors"
  }
}

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.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety and idempotency profile is fully covered and the description does not contradict it. The description adds only a hint about returned content, not behavior such as scoping, translation fallback, or completeness of the result set.

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

Conciseness3/5

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

It is a single short fragment with no wasted words, but the terseness comes at the cost of a missing verb and any operational context. Brevity here reads as under-specification rather than disciplined concision.

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

Completeness2/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 no output schema, the annotations carry the safety profile, yet the description still omits what the tool actually does, that results are filtered by the required trust center, and that translation can change the output language. An agent cannot confirm correct invocation from this text alone.

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%, with both the trust_center identifier (including the fallback to domain or exact company name) and the language code range fully documented in the schema. The description contributes no additional parameter meaning, so the baseline of 3 applies.

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 fragment ('Subprocessors with purpose, location and transfer mechanism') that names the resource and its returned attributes but never supplies a verb, so the agent must infer that this is a read/list operation from the tool name alone. It does add the useful detail of what fields are surfaced, which keeps it above pure tautology.

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 when-to-use guidance, no mention of alternatives among the many sibling list_* tools, and no exclusions. The only implicit context is that it concerns subprocessors, leaving the agent to reason about selection entirely from the name.

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