Skip to main content
Glama
arturayupov

Lextiva Compliance MCP Server

list_data_subject_rights

Returns the eight canonical data-subject rights and the regulations that grant each, covering access, rectification, erasure, portability, and more.

Instructions

Returns the list of the 8 canonical data-subject rights and the regulations that grant each: access, rectification, erasure, portability, restriction, objection, opt_out_sale_or_sharing, automated_decision_making.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Without annotations, the description carries full burden. It accurately describes the output (rights and regulations) without hiding any behaviors; a simple list retrieval is transparent enough.

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?

Single sentence, no fluff. Every word adds value: specifies the exact 8 rights and the associated regulations.

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?

For a zero-parameter list tool, the description is complete. It enumerates all rights and mentions regulations, leaving no ambiguity about the output.

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?

No parameters exist; the description adds value by explaining what the output contains, going beyond the empty schema.

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 states the tool returns the list of 8 canonical data-subject rights and the regulations that grant each, distinguishing it from sibling tools like 'get_data_subject_right' which retrieves a single right.

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?

The description implies the tool is for listing all rights, but does not explicitly state when to use it over siblings like 'applicable_regulations' or provide exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/arturayupov/lextiva-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server