Skip to main content
Glama

The legal path behind one obligation, not only the outcome

explain_applicability
Read-only

Use this whenever you have to justify why an obligation does or does not bear on a case, and an outcome on its own is not enough. It returns the legal path: the conditions under which the rule is about a situation, the exceptions under which it is not despite those conditions, and the statements of the obligation split by kind, each with the primary source, the locator inside that source and the source record behind it. Supply a profile as well and the deterministic rule trace is added: which rule was met, not met or unknown for this case, plus the assumptions and the questions the engine could not settle. Use this rather than paraphrasing an obligation yourself: the conditions, the exceptions and the citations are published data and are not to be reconstructed from prose. Take the identifier from earlier tool output; a short form such as art. 26 resolves when it points at one obligation, else error_code and suggestions come back. A question without an identifier belongs with the short question tool or the case check.

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": {
      "obligation_id": "<obligation_id>"
    },
    "name": "explain_applicability"
  }
}

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
profileNoThe 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.
known_atNoKnowledge time pin, a date or an ISO instant. Defaults to the release default.
effective_atNoLegal time pin, a date or an ISO instant. Defaults to the release default.
obligation_idYesThe stable identifier, for example praxikon:eu:ai-act:obligation:article-50-transparency.
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
pinNoThe release and the two time axes this answer resolved against. Store it next to anything you keep: an unpinned query is not reproducible, because the defaults move with each release.
viewNo
caveatsNo
messageNo
sourcesYes
assessmentYesPresent only when a profile was supplied and the decision engine assessed this obligation for it. Null otherwise, with the reason in assessment_absent_reason and, when the engine said why, the detail in not_assessed.
error_codeNo
legal_pathYes
obligationYes
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.
suggestionsNo
not_assessedNoWhy the engine did not assess this obligation for this profile, as the engine reported it, with the facts that would have it assessed. For example profile_version_below_2: send a version 2 profile.
requested_idNo
identifier_resolutionNo
assessment_absent_reasonNo

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. Changed5 schema fields changed
    • addedOutput schema / properties / error_code
      Added value: +{
      +  "enum": [
      +    "unknown_identifier",
      +    "ambiguous_identifier"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / identifier_resolution
      Added value: +{
      +  "type": "object"
      +}
    • addedOutput schema / properties / message
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / requested_id
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / suggestions
      Added value: +{
      +  "type": "array"
      +}
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnly/non-destructive/closed-world, so the safety profile is already covered. The description still adds real behavior: deterministic rule traces are only produced when a profile is supplied, the trace reports met/not-met/unknown plus unresolved assumptions and questions, ambiguous short identifiers yield error_code with suggestions, and the profile is server-validated against classify_system's schema. It omits anything about response size, latency or pagination, keeping it from 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?

Front-loaded with the when-to-use clause, then the return contents, then the alternative routing — a sensible order. Sentences are dense and compound ('the conditions under which the rule is about a situation, the exceptions under which it is not despite those conditions...'), which slows parsing slightly, but no sentence is filler.

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?

For a 7-parameter tool with a nested profile object and an output schema, the description covers the essential decision inputs: when to call it, how to obtain the identifier, what the optional profile unlocks, how ambiguity fails, and where to go instead. Return-value detail is legitimately delegated to the existing output schema.

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%, so baseline is 3, but the description earns above baseline by explaining that profile is the same coded profile classify_system accepts and that a version-2 profile widens the assessed set (including Article 26 for a deployer). It also explains short-form identifier resolution for obligation_id ('art. 26' resolves when unambiguous, otherwise error_code and suggestions).

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 states a specific resource and scope: it returns the legal path behind ONE obligation — the conditions, the exceptions, and the obligation statements split by kind with source, locator and source record. It distinguishes itself from siblings both positively ('use this rather than paraphrasing an obligation yourself') and by routing questions without an identifier to 'the short question tool or the case check'.

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

Usage Guidelines5/5

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

The when-to-use condition is explicit and conditional: justify whether an obligation bears on a case when an outcome alone is insufficient. It adds a negative case ('a question without an identifier belongs with the short question tool or the case check') and a prerequisite ('take the identifier from earlier tool output'), which is exactly the routing an agent needs.

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