mcpforwork

Overview Schema Source Related Servers Discussions Admin

export_my_data

Export all stored personal data (profile, applications, audit trail) as a single JSON object to comply with GDPR data portability.

Instructions

GDPR data portability: everything stored about you (profile, findings, applications, assets, audit trail) as one JSON object. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "export_my_data"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states 'Read-only,' which is a key safety trait, and lists what data is included, offering transparency about the operation's scope. It does not mention potential large response size or auth requirements, but the read-only nature and content breakdown provide solid context.

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, well-structured sentence that leads with the regulatory context ('GDPR data portability'), immediately clarifies the output ('one JSON object'), and enumerates included data types. Every element earns its place with no filler.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (zero params) and has an output schema available, so the description need not explain return values. It covers the key aspects: what is exported, in what form, and that it is read-only. This is complete for the tool's complexity.

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?

The tool has zero parameters, so the schema provides full coverage (100%). The description adds no parameter details, but none are needed. Baseline for 0 params is 4, and the description appropriately focuses on the output and purpose.

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?

The description clearly identifies the tool's function: exporting all stored data about the user for GDPR data portability. It specifies the verb ('export'), the resource ('everything stored about you'), and provides concrete content categories (profile, findings, applications, assets, audit trail), distinguishing it from sibling tools like get_profile or delete_my_data.

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?

The description sets clear context for use—GDPR data portability—and implies this is the comprehensive export tool for a full copy of user data. It does not explicitly mention alternatives or when not to use it, but the scope is unambiguous. This is clear context without exclusions.

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