Skip to main content
Glama

Praxikon

Which obligations the decision engine indicates for one system

get_applicable_obligations
Read-only

Use this when you need the obligations themselves for one assessed system rather than the classification picture: which obligations apply, which possibly apply, from when, why, and on which source and locator. Returns one entry per assessed obligation, filtered by applicability. A version 2 profile has the wider set assessed, including Article 26 for a deployer of a high risk system, with one sub result per paragraph. This is the assessed route, not a catalogue of all obligations in the dataset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoLanguage of the labels and explanations. Dutch is the default.nl
detailNoAmount 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.brief
profileYesThe same coded profile that classify_system takes, with the same fields and codes: see the profile schema of classify_system. Send a version 2 profile to have the wider set assessed, including Article 26 for a deployer. The server validates the profile against that full schema.
applicabilityNoWhich applicability statuses to return. Defaults to applies and possibly_applies. The counters and evaluated_obligation_ids stay complete whatever you filter on, so a filtered list can never be read as the whole assessment.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
viewNo
datasetNo
sourcesNo
summaryYes
disclaimerNo
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.
filtered_onNo
obligationsYes
snapshot_idNo
deadline_notesNo
assessment_scopeNoWhat this assessment did and did not assess, from the engine itself. not_assessed groups the obligations that were not assessed by reason (for example profile_version_below_2), with the facts that would have them assessed. Not assessed is not the same as not applying.
evaluation_scopeNo
decision_engine_versionNo
evaluated_obligation_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources