Skip to main content
Glama

Export consent

export_consent
Read-onlyIdempotent

The suppression list, or the full consent ledger with opt-in proof, as CSV text.

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_consent"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNosuppressions: the opted-out numbers. ledger: every consent record, with proofsuppressions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / type / description
      Added value: +"suppressions: the opted-out numbers. ledger: every consent record, with proof"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description's real contribution is disclosing the return shape — CSV text — which the annotations cannot express. It says nothing about export size, streaming, or whether the ledger export is costly.

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?

A single telegraphic clause with zero padding, and the resource is front-loaded ahead of the format. It is slightly under-specified as a fragment with no verb, which keeps it from a 5.

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 one-optional-param read tool with no output schema, the description supplies the essential missing piece: that the result is CSV text rather than a JSON array of records. What remains unstated (export size limits, whether the ledger is paged) is minor for this complexity level.

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% and the single parameter's enum values are documented in detail there. The description's 'with opt-in proof' phrasing merely echoes that enum text, adding no new syntax, defaults, or edge-case meaning. Baseline 3 applies when the schema does the heavy lifting.

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 the resource (consent data) and enumerates the two exportable variants — the suppression list and the full consent ledger with opt-in proof — plus the output format (CSV text). It is a noun phrase rather than a verb+resource sentence, and it does not distinguish itself from siblings like export_csv or list_opt_outs.

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 statement of when to use this tool versus export_csv, list_opt_outs, or get_consent, nor any exclusions or prerequisites. The only choice guidance (suppressions vs ledger) is already carried by the enum description in the schema, not by this text.

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.