Skip to main content
Glama

Get an obligation

get_obligation
Read-onlyIdempotent

Get one row of the obligation register by its stable id (e.g. "AIGE-OBL-EUAIA-ART9", any case) or its page URL: the requirement, the artefact that evidences it, the stack layers, duty holder, application date and later milestones, the patterns that implement it, the crosswalk references joined to it, and the chapter 08 section it comes from.

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": {
      "id": "<id>"
    },
    "name": "get_obligation"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesObligation id or URL.

Output Schema

NameRequiredDescriptionDefault
idYes
urlYesCanonical page of the obligation.
jsonYes
scopeYesWho the row binds, for laws outside the EU AI Act.
clauseYes
layersYes
noticeYesIllustrative, not legal advice and not a claim of conformity.
sourceYesCanonical URL of the page this answer comes from; cite it.
chapterYesChapter 08 section the row comes from.
datasetYesURL of the open-data document the answer was read from.
licenseYesLicence of the data (CC BY 4.0, attribution required).
artefactYesThe engineering artefact that evidences the obligation.
patternsYesPatterns that implement the obligation, with their pattern pages.
reviewedYes
authorityYes
crosswalkYes
frameworkYes
dutyHolderYes
milestonesYes
obligationYes
appliesFromYesFirst application date (ISO), null when voluntary or undated.
appliesNoteYes
dataVersionYesBody of Knowledge version of the data.
frameworkIdYes
requirementYes
systemClassYes
appliesStatusYes
frameworkInfoYes
crosswalkTopicsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: ids are case-insensitive, a page URL is an accepted alternative key, and the row carries joined crosswalk and pattern references. It does not say what happens for an unknown id, which keeps it short of a 5.

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?

A single front-loaded sentence that leads with the verb, the resource and the accepted keys before enumerating returned content. The trailing field enumeration is long but each item names a distinct payload component, so little is wasted.

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 an output schema present, the description need not document return shapes, yet it still gives a useful preview of the joined data (requirement, evidence artefact, stack layers, duty holder, milestones, patterns, crosswalks, chapter 08 section). What remains missing is failure behavior for an unresolvable id or URL.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema only says 'Obligation id or URL', so the description is what clarifies that the string may be either form, that matching is case-insensitive, and gives a concrete example format. That is meaningful added meaning over the schema, though it omits the 3–200 length bounds already in 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 ('Get one row of the obligation register') and pins down the lookup keys (stable id or page URL). The singular 'one row' plus the id-based lookup clearly separates it from the plural list sibling get_obligations without needing to name it.

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 only implied: the agent can infer this is the tool to reach for when it already holds an obligation id or URL, reinforced by the example id. There is no explicit when-to-use vs get_obligations/search_bok guidance and no statement about what to do when the id is unknown or missing.

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.