Cookie Compliance

OBSOLETE — renamed to help.explainConfigKey

demo.explainConfigKey

Read-only

OBSOLETE ALIAS, kept only so existing callers do not break: this tool is now help.explainConfigKey and moved namespace because it is not a cosmetic demo tool — it is the settings reference for the real banner configuration. It still works and returns exactly the same answer. Call help.explainConfigKey instead; this name will be retired.

Input Schema

Name	Required	Description	Default
`key`	No	One key to explain. Accepts a bare name (`blocking`, `bodyText`, `bannerBackground`) or a dotted path exactly as the preview tools take it (`config.blocking`, `config.regulations.gdpr`, `design.primaryColor`, `text.bodyText`, `consentConfig.*`). Every match is returned when a bare name exists in more than one vocabulary.
`list`	No	Enumerate a whole vocabulary instead of explaining one key: `config` (the 70 BannerConfigJSON settings, each with its tier and consequence), `regulations`, `consentConfig`, `design`, `text`, `snippet` (the huOptions keys that go in the page, including `blocking`, plus preview-only keys that must never go in the page), or `all`. Use this to find out WHICH setting does what you want before naming one — start with `config` for anything about consent categories, geolocation, consent mode or GPC.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

changedInput schema / properties / list / description

Previous value: -"Enumerate a whole vocabulary instead of explaining one key: `config` (the 70 BannerConfigJSON settings, each with its tier and consequence), `regulations`, `consentConfig`, `design`, `text`, `snippet` (the huOptions keys that go in the page, including `blocking`), or `all`. Use this to find out WHICH setting does what you want before naming one — start with `config` for anything about consent categories, geolocation, consent mode or GPC."New value: +"Enumerate a whole vocabulary instead of explaining one key: `config` (the 70 BannerConfigJSON settings, each with its tier and consequence), `regulations`, `consentConfig`, `design`, `text`, `snippet` (the huOptions keys that go in the page, including `blocking`, plus preview-only keys that must never go in the page), or `all`. Use this to find out WHICH setting does what you want before naming one — start with `config` for anything about consent categories, geolocation, consent mode or GPC."

Changed1 schema field changedOct 2, 2026

changedInput schema / properties / list / description

Previous value: -"Enumerate a whole vocabulary instead of explaining one key: `config` (the 69 BannerConfigJSON settings, each with its tier and consequence), `regulations`, `consentConfig`, `design`, `text`, `snippet` (the huOptions keys that go in the page, including `blocking`), or `all`. Use this to find out WHICH setting does what you want before naming one — start with `config` for anything about consent categories, geolocation, consent mode or GPC."New value: +"Enumerate a whole vocabulary instead of explaining one key: `config` (the 70 BannerConfigJSON settings, each with its tier and consequence), `regulations`, `consentConfig`, `design`, `text`, `snippet` (the huOptions keys that go in the page, including `blocking`), or `all`. Use this to find out WHICH setting does what you want before naming one — start with `config` for anything about consent categories, geolocation, consent mode or GPC."

Changed3 schema fields changedSep 10, 2026

changedInput schema / properties / key / description

Previous value: -"A huOptions.design.* or huOptions.text.en.* key to explain."New value: +"One key to explain. Accepts a bare name (`blocking`, `bodyText`, `bannerBackground`) or a dotted path exactly as the preview tools take it (`config.blocking`, `config.regulations.gdpr`, `design.primaryColor`, `text.bodyText`, `consentConfig.*`). Every match is returned when a bare name exists in more than one vocabulary."

addedInput schema / properties / list

Added value: +{
+  "description": "Enumerate a whole vocabulary instead of explaining one key: `config` (the 69 BannerConfigJSON settings, each with its tier and consequence), `regulations`, `consentConfig`, `design`, `text`, `snippet` (the huOptions keys that go in the page, including `blocking`), or `all`. Use this to find out WHICH setting does what you want before naming one — start with `config` for anything about consent categories, geolocation, consent mode or GPC.",
+  "enum": [
+    "config",
+    "regulations",
+    "consentConfig",
+    "design",
+    "text",
+    "snippet",
+    "all"
+  ],
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "key"
-]
```

First observedSep 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description usefully adds lifecycle context: it is kept for backwards compatibility, returns exactly the same answer, and will be retired. It stops short of describing the shape of the returned explanation, which is the one behavioral gap for a tool with no output schema.

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?

The deprecation status is front-loaded and the key facts (obsolete, still works, use the other name, will be retired) arrive in order. There is mild redundancy in restating that it still works and returns the same answer, but nothing is wasted.

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 deprecated alias with full schema coverage and no output schema, the description covers everything an agent needs: identity, equivalence, and the correct replacement. Only the return shape is left implicit, which is minor given the tool simply forwards to help.explainConfigKey.

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 both parameters (key, list) carry rich, self-contained descriptions including enum semantics and usage hints, so the description correctly does not repeat them. Baseline 3 is appropriate since the description adds no parameter meaning of its own.

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 states the tool's identity and function plainly: an OBSOLETE ALIAS that is now the settings reference for the banner configuration, and it names the exact replacement (help.explainConfigKey) so an agent can distinguish it from that sibling without opening either schema.

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?

It gives explicit routing: "Call `help.explainConfigKey` instead; this name will be retired," while also noting the alias still works for existing callers. Both the when-to-use (legacy callers only) and the preferred alternative are spelled out.

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

All Cookie Compliance 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?