Skip to main content
Glama

NovaPixel LexGrid

eu_ai_act_check

Inspects DOM and scripts for user-facing AI/chatbot systems (OpenAI, Anthropic, Intercom Fin, Voiceflow, Botpress) and verifies Article 50 transparency disclosure compliance.

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": "eu_ai_act_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoTarget website URL to inspect
htmlContentNoRaw HTML content of page/widget

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It says what is inspected but not how it behaves: whether the URL is fetched server-side, whether htmlContent is a substitute for url or an addition, and what the inspection produces (a pass/fail verdict, per-check findings, detected vendors) is left unstated.

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?

A single dense sentence with the verb and scope front-loaded and no filler. The vendor list is the only lengthy element and it earns its place by defining detection coverage.

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

Completeness3/5

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

With no annotations and no output schema, the description should describe what a caller gets back from a compliance verification, and it does not. It is adequate on scope but incomplete on result shape, and the two-parameter input model (url vs htmlContent) is not resolved anywhere in the definition.

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 both parameters are already documented in the schema and the baseline of 3 applies. The description adds no meaning beyond that, notably not clarifying whether url and htmlContent are alternative input modes or whether one is required despite the zero required-parameter count.

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?

Names a specific verb ("Inspects"), a specific resource (DOM and scripts), a concrete target class (user-facing AI/chatbot systems, with named vendors), and a concrete standard (Article 50 transparency disclosure). The domain is distinct enough from cookie_dark_patterns and gdpr_cmp_tracker_audit to be told apart, but the description never states that differentiation explicitly.

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?

There is no explicit when-to-use sentence, no exclusions, and no named alternative among the sibling tools. Usage is only implied by the mention of AI/chatbot systems and Article 50 compliance, which is enough to infer intent but leaves the agent to decide on its own when this tool is preferable to the CMP or cookie auditors.

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.

Resources