Skip to main content
Glama
kanibal-studio

kanibal-tools-mcp

Official
by kanibal-studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

check_telemarketing_consent

Read-onlyIdempotent

Check whether French telemarketing consent remains valid under décret 2026-662, returning status, expiry date, and proof-retention date, and failing closed on missing or future collection dates.

Instructions

France only: is a consent to telephone canvassing still valid under décret 2026-662?

Returns "valide", "expire" (older than the ceiling), "revoque" (any sign of
revocation wins) or "preuve_manquante" (no readable collection date, or one in the
future), with the expiry date and proof-retention date. Fail-closed. Use it for
French telemarketing consent only; for transfers of customer-service data outside
the EU use gdpr_offshore_gap_report. Not legal advice.

Input Schema

NameRequiredDescriptionDefault
nowNoReference instant, ISO 8601; defaults to the current UTC time.
revoked_atNoRevocation date or any sign of revocation; omit if none.
collected_atYesWhen the consent was collected, ISO 8601; a date without time zone is read as UTC.
max_age_daysNoStricter internal ceiling in days; values above 365 or not positive fall back to the legal 365.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / collected_at / description
      Added value: +"When the consent was collected, ISO 8601; a date without time zone is read as UTC."
    • addedInput schema / properties / max_age_days / description
      Added value: +"Stricter internal ceiling in days; values above 365 or not positive fall back to the legal 365."
    • addedInput schema / properties / now / description
      Added value: +"Reference instant, ISO 8601; defaults to the current UTC time."
    • addedInput schema / properties / revoked_at / description
      Added value: +"Revocation date or any sign of revocation; omit if none."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the complete outcome enum, the fail-closed posture, and the extra artifacts returned (expiry date, proof-retention date). The revocation-wins precedence rule is a behavioral trait an agent could not infer from structured fields.

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?

Front-loads jurisdiction and question in the first line, then outcomes, then routing to the sibling tool. Every sentence carries distinct information; the legal disclaimer is short and earns its place.

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?

With an output schema present, the description needn't document return shape, and it still names the result values. Combined with full schema coverage and safety annotations, nothing needed to call this correctly is missing.

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%, so the schema already documents all four parameters including the 365-day fallback and UTC assumption. The description adds only the ceiling/expiry framing and revocation precedence, which is a marginal increment over the schema — baseline 3 applies.

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 (validating telemarketing consent), pins the jurisdiction (France only) and the legal instrument (décret 2026-662). An agent can immediately distinguish this from the sibling GDPR report tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly scopes usage ("Use it for French telemarketing consent only") and names the alternative tool with its triggering condition (EU-outside transfers → gdpr_offshore_gap_report). Both when-to-use and when-not-to-use are stated.

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

Deploy Server

Other Tools