Skip to main content
Glama
Sign In

Spurvik EU AI Act

by com.spurvik
OverviewDiscussionsAdmin

spurvik_scan_live_url

Read-onlyIdempotent

Scan one public HTTPS page for AI chat widgets and AI SDKs and check whether a visible EU AI Act Article 50(1) notice is present. Returns the host, HTTP status, findings, the suggested notice language, a one-line badge.js fix and links to the full report. Heuristic: reads the HTML of one page only. Not legal advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "spurvik_scan_live_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic domain or https URL, for example stepnetwork.dk.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real behavioral value beyond that: the heuristic limitation ('reads the HTML of one page only', implying no rendered/JS-executed crawling), the expected response payload, and a 'Not legal advice' caveat.

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?

Four sentences, front-loaded with what the tool does, followed by the return payload, the heuristic caveat, and the disclaimer. No filler or repetition, and each sentence contributes distinct information.

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?

With no output schema, the description correctly takes on the burden of describing the return payload (host, status, findings, notice language, fix, report links), and it discloses the single-page HTML-only limitation. Minor gaps remain around failure modes (e.g. non-HTTPS or unreachable hosts) and scan latency.

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% for the single `url` parameter, including an example, so baseline 3 applies. The description reinforces the constraint to public HTTPS pages but adds no syntax, normalization, or error-handling detail beyond the schema.

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 ('Scan one public HTTPS page for AI chat widgets and AI SDKs') plus the concrete check performed ('whether a visible EU AI Act Article 50(1) notice is present'). Scope ('one public HTTPS page') and the diagnostic-vs-generative distinction from siblings like spurvik_generate_art50_badge are clear.

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?

Usage is implied rather than stated: 'one page only' and 'public HTTPS page' bound the input, and the mention of a 'badge.js fix' hints that this is the diagnostic step before remediation. However, no sibling is named and there is no explicit when-to-use/when-not-to-use guidance (e.g. versus spurvik_find_unwrapped_calls or a site-wide scan).

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

All Spurvik EU AI Act toolsInspect
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