Skip to main content
Glama

obligations_for_use_case

Read-only

Retrieve EU AI Act obligations for a given AI use case, when each applies, and whether supporting evidence exists. Identify compliance gaps per use case.

Instructions

AI Act obligations for one AI use case, when they apply, and whether evidence exists for each.

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": {
      "use_case_id": "<use_case_id>"
    },
    "name": "obligations_for_use_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
use_case_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that results include applicability conditions and an evidence-exists flag per obligation, which is genuine behavioral context, but says nothing about permissions, error cases, or what happens for an unclassified use case.

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?

A single front-loaded sentence with no filler; every clause (obligations, when they apply, evidence existence) carries distinct meaning.

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?

An output schema exists, so return values need not be explained, and the tool is simple with one parameter. What is missing is only the origin/format of use_case_id and behavior for a use case with no prior classification.

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?

There is one required parameter with 0% schema description coverage, so the description must carry it. It implies use_case_id identifies a single AI use case, but gives no format, no source (e.g. from list_applications or classify_use_case), and no guidance on invalid IDs.

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 names the resource (AI Act obligations) and the scope precisely (one AI use case), and adds the two dimensions returned: applicability conditions and per-obligation evidence status. That distinguishes it reasonably from evidence_gaps and portfolio_exposure, though it does not explicitly name the sibling it is not.

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 singular 'one AI use case' signals a per-use-case lookup rather than a portfolio query. There is no explicit when-to-use, no prerequisite (e.g. the use case must already be classified), and no pointer to alternatives such as evidence_gaps or classify_use_case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.