Skip to main content
Glama
Sign In

Spurvik

by io.github.spurvik
OverviewDiscussionsAdmin

spurvik_generate_art50_badge

Read-onlyIdempotent

Generate a copy-paste EU AI Act Article 50 notice: a badge.js tag or a React snippet, in any of the 24 EU languages, with a preview of the notice text. The language is inferred from a domain-like systemName when locale is omitted.

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": {
      "systemName": "<systemName>"
    },
    "name": "spurvik_generate_art50_badge"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeNo
formatNo
localeNo
noticeNo
placementNo
systemNameYesProduct or assistant name, or the site domain.
whitelabelNoHide the Spurvik trust link (Pro or Done-For-You).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world generation operation. The description adds useful behavior beyond that: it returns copy-paste snippets plus a preview, supports 24 EU languages, and falls back to inferring language from a domain-like systemName when locale is omitted.

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?

Two dense sentences front-load the core output, list the two snippet formats, state language coverage, and explain the locale fallback. There is no redundant or wasted wording.

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?

For a seven-parameter generation tool with no output schema and low schema description coverage, the definition covers the main output and locale behavior but omits return-shape details, placement/theme effects, and notice-type distinctions. It is adequate but has clear gaps.

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 only 29%, so the description must compensate for several undocumented parameters. It does explain format outputs, language breadth, and locale inference from systemName, but it leaves the notice, theme, placement, and whitelabel semantics largely to 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?

The description uses a specific verb and resource: generate an EU AI Act Article 50 notice as either a badge.js script tag or a React AIDisclosureLabel snippet. It also states the language scope and preview output, so an agent can tell exactly what this tool produces.

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 description implies when the tool is useful — generating copy-paste AI Act disclosure notices — but it does not explicitly say when to choose it over siblings such as spurvik_setup_snippet or spurvik_marking_hooks. No when-not guidance or prerequisites are stated.

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

All Spurvik 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