Skip to main content
Glama

Who supervises, per member state

get_national_enforcement
Read-only

Use this for the national layer: which authority is designated in a member state, how far the implementing law has come, and which dated enforcement signals are recorded, each with a primary source. The authority is recorded as free text per member state and is deliberately not a graph identifier, because which national body fills the market surveillance role differs per member state. The same call returns the ruling register: judgments and supervisory decisions with the relation they bear to a provision (interprets, narrows, broadens, confirms, contradicts, or illustrates for context). An event says what happened, a ruling says what we know a provision means. Never present a related_gdpr ruling as AI Act case law: it rests on the GDPR and carries the illustrates relation only. This tool takes no lang: the tracker carries both languages on every record, in the fields that end in _nl and _en.

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

Input Schema

NameRequiredDescriptionDefault
typeNoNarrow to one event type, for example implementing_law.
detailNobrief keeps the outcome, dates, reasons, open questions and the source with its locator; full adds the complete objects, statement texts and hashes, for re-computation or archiving.brief
countryNoISO 3166-1 alpha-2 country code, for example NL. Omit for all member states.
known_atNoKnowledge axis of the ruling register, as YYYY-MM-DD: returns the rulings we had recorded on that date and nothing that arrived afterwards. A provision keeps its own effective_at; only the reading moves.
obligationNoSlug of an obligation, for example article-50-transparency. Returns the rulings that bear on it. An empty result on an existing obligation means no ruling is recorded, not that the slug is wrong.
store_for_improvementNoOptional. Set to false when the user asks that Praxikon does not keep this request to improve its answers; only the anonymous daily count remains. See https://www.praxikon.com/nl/legal/privacy, section 2.7.

Output Schema

NameRequiredDescriptionDefault
viewNo
statsNo
eventsYes
filtersNo
rulingsYes
versionNo
countriesYes
provenanceYesWhich published endpoints produced this result. Every call is listed with its full URL, so a reader can re-issue it and check the answer rather than trust it.
verified_atNo
events_totalNo
ruling_registerNo
empty_result_noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / detail / description
      Previous value: -"Amount of data to return. brief keeps the outcome, the dates, the reasons, the open questions and the source with its locator; full adds the complete objects, every statement text and every hash, for re-computation or archiving."New value: +"brief keeps the outcome, dates, reasons, open questions and the source with its locator; full adds the complete objects, statement texts and hashes, for re-computation or archiving."
    • changedInput schema / properties / store_for_improvement / description
      Previous value: -"Optional. Set to false when the user asks that Praxikon does not keep this request to improve its answers; nothing of this call is then kept beyond the anonymous daily count. See https://www.praxikon.com/nl/legal/privacy, section 2.7."New value: +"Optional. Set to false when the user asks that Praxikon does not keep this request to improve its answers; only the anonymous daily count remains. See https://www.praxikon.com/nl/legal/privacy, section 2.7."
  2. Changed1 schema field changed
    • addedInput schema / properties / store_for_improvement
      Added value: +{
      +  "default": true,
      +  "description": "Optional. Set to false when the user asks that Praxikon does not keep this request to improve its answers; nothing of this call is then kept beyond the anonymous daily count. See https://www.praxikon.com/nl/legal/privacy, section 2.7.",
      +  "type": "boolean"
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly and non-destructive annotations, the description discloses important behavior: authority names are free text per member state, the ruling register uses relation types such as interprets, narrows, and broadens, events and rulings have different epistemic status, and related_gdpr rulings must not be framed as AI Act case law. It also explains the language behavior, noting there is no lang parameter because every record carries _nl and _en fields.

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?

The description is front-loaded with the tool's purpose and then layers in the authority model, ruling register semantics, and the GDPR caveat. Every sentence carries specific information that an agent would need to interpret the output correctly, with no filler or repetition.

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

Completeness5/5

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

Given the complexity of a national enforcement and ruling register, the description covers the data model, the distinction between events and rulings, the relation taxonomy, the source-backed nature of the records, and the language convention. An output schema exists, so return values need not be explained in detail, and the annotations already carry the safety profile.

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 the input schema already documents each parameter thoroughly, including the detail enum, country code format, known_at semantics, and obligation slug. The description adds only the absence of a lang parameter and the bilingual field convention, which is useful but does not substantially deepen the meaning of the six declared parameters.

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 clearly states the national layer content: designated authority, implementing law progress, dated enforcement signals, and the ruling register. It distinguishes events from rulings and explains the authority is free text rather than a graph identifier. It does not explicitly differentiate itself from sibling tools such as get_applicable_obligations or get_source_provenance, which keeps it from a 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 phrase 'Use this for the national layer' gives an implied scope for when to call the tool. The caveat about never presenting related_gdpr rulings as AI Act case law is a useful usage constraint, but the description names no alternatives and provides no explicit when-not-to-use guidance relative to siblings.

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