Skip to main content
Glama

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.

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": {
      "profile": "<profile>"
    },
    "name": "get_applicable_obligations"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the labels and explanations. Dutch is the default.nl
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
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.
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
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. 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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, non-destructive and closed-world, so safety is covered. The description adds useful structural behavior: one entry per assessed obligation, filtered by applicability, and a wider assessed set with one sub-result per paragraph for version 2 profiles. It stops short of noting performance, error behavior, or what an empty filtered result means beyond what the schema says.

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?

The when-to-use condition is front-loaded and the two sentences are dense but purposeful, with no filler. The Article 26 example is slightly deep in the weeds for a description, but it earns its place by clarifying output shape differences.

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?

For a tool with a nested profile object, an output schema and strong annotations, the description supplies the route context, scope, and profile-version nuance an agent needs to choose and call it. The remaining gap is only sibling routing on the alternatives listed in the toolset.

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 baseline is 3 and the schema already carries the parameter details, including the applicability filter caveat about counters. The description adds some meaning for the profile parameter by explaining the version 2 consequence (Article 26 for a deployer, one sub-result per paragraph), which is real value but limited to one parameter.

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 states a specific verb and resource: the obligations themselves for one assessed system, naming what is returned (which apply, which possibly apply, from when, why, source and locator). It distinguishes itself from the classification route ('rather than the classification picture') and from a full catalogue, though it never names the sibling tools (classify_system, explain_applicability) explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit when-to-use trigger ('when you need the obligations themselves for one assessed system') and a clear exclusion via the closing sentence contrasting it with a catalogue of all obligations. What is missing is routing on sibling names, e.g. when to prefer explain_applicability or classify_system instead.

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