SAGOT

platform_subprocessors_notify

Platform staff only (account session). Requires manage. Email every workspace owner (one email per person) that SAGOT will add or replace a sub-processor on effectiveOn — at least 30 days ahead, as the Data Processing Addendum promises — with how to object. Describe what changes, its purpose and location in change. Audited.

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": {
      "change": "<change>",
      "effectiveOn": "<effectiveOn>"
    },
    "name": "platform_subprocessors_notify"
  }
}

Input Schema

Name	Required	Description	Default
`change`	Yes
`effectiveOn`	Yes	YYYY-MM-DD, at least 30 days from today (UTC).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and delivers: staff-only auth, required 'manage' permission, a fan-out side effect (one email per workspace owner), the 30-day lead requirement, and that the action is audited. It omits success/response behavior and idempotency, but the operation's effects and constraints are well disclosed.

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 but front-loaded paragraph leading with the staff/manage constraint, then the effect, then parameter guidance. Every clause carries information, though the em-dash-embedded legal rationale makes it slightly run-on.

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?

For a two-parameter tool with no annotations, no output schema, and partial schema coverage, the description covers permissions, side effects, timing, parameter intent, and audit status. Only return/response behavior is unstated, a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50% ('change' has no schema description), but the description compensates by defining what belongs in 'change' (what changes, its purpose, and location) and ties 'effectiveOn' to the 30-day-ahead rule. This adds real meaning beyond the schema's min/max bounds.

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?

States a specific verb and resource: email every workspace owner that SAGOT will add or replace a sub-processor. No sibling tool does anything similar, so an agent can select it unambiguously.

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?

Explicitly scopes usage with 'Platform staff only (account session). Requires manage.' and imposes a timing precondition ('at least 30 days ahead'). It does not name alternatives, but no comparable sibling exists, so the guidance is effectively complete.

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

All SAGOT tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?