Skip to main content
Glama

eu_ai_act_check

Read-onlyIdempotent

[Web DOM inspection. Read-only, non-destructive, side-effect free]. Inspects website scripts, widgets, and DOM elements for user-facing generative AI/chatbot interfaces (OpenAI, Anthropic, Intercom Fin, Voiceflow, Botpress) and verifies mandatory Article 50 EU AI Act transparency disclosures. Usage: Use this tool to evaluate user-facing artificial intelligence systems for statutory transparency compliance under the EU AI Act. Returns: JSON object with { aiSystemsDetected: string[], hasArticle50Disclosure: boolean, disclosureSnippet: string | null, riskLevel: 'MINIMAL' | 'SPECIFIC_TRANSPARENCY' | 'HIGH', complianceNotes: string[] }.

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 (e.g. https://novapixel.it)
htmlContentNoRaw HTML content of page/widget

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Target website URL to inspect"New value: +"Target website URL to inspect (e.g. https://novapixel.it)"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With annotations already declaring readOnlyHint and idempotentHint, the description adds meaningful context beyond them: it names the specific detection targets (OpenAI, Anthropic, Intercom Fin, Voiceflow, Botpress) and enumerates the returned fields including a risk classification. It does not say whether a live URL is actually fetched, whether there are rate limits or network/auth constraints, or how url and htmlContent interact, so it is not fully transparent.

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 three-part structure (bracketed trait summary, Usage, Returns) is front-loaded and easy to scan, and no sentence is wasted. The bracketed 'read-only, non-destructive, side-effect free' preamble largely restates the annotations, which is minor redundancy rather than bloat.

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?

There is no output schema, but the description fully enumerates the return object's fields and their types, so an agent knows what to expect. The remaining gap is operational: how url and htmlContent relate and what happens when detection finds nothing are unexplained. For a two-parameter read-only inspection tool, it is otherwise complete.

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%, with both url and htmlContent documented in the schema, so the baseline is 3. The description adds no parameter-level meaning at all, notably nothing about which parameter takes precedence, whether one is required in practice, or the expected format of htmlContent. The schema carries the entire burden.

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 uses a specific verb and resource set: it inspects website scripts, widgets and DOM elements for generative AI/chatbot interfaces from named vendors and verifies Article 50 EU AI Act transparency disclosures. That is far more concrete than a restated title. It does not explicitly differentiate itself from its siblings (b2b_tech_profiler, cookie_dark_patterns, gdpr_cmp_tracker_audit), which is why it lands at 4 rather than 5.

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 'Usage' line gives a clear context: evaluate user-facing AI systems for statutory transparency compliance under the EU AI Act. However, it offers no when-not guidance, no prerequisites, and does not point to any alternative tool for related audits. Usage is implied well enough to pick the tool for its main case, but exclusions are absent.

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