Skip to main content
Glama

Answer a short general question about the AI Act or the GDPR

answer_question
Read-only

Use this for a short, general question about the EU AI Act or the GDPR (AVG), such as whether a customer service chatbot has to say that it is AI or when a DPIA is required. It looks the question up in the published Praxikon answers: deterministic, no language model, and with the articles and sources. Before you call it, rewrite the question in general terms in at most 200 characters: no names of people or organisations, no contact details, no numbers that identify a person or a case. A question that looks like it contains personal data is refused. The question never goes into a URL, a server log or an analytics service. Praxikon may keep it, after a filter for personal data, to improve its answers, unless store_for_improvement is false (privacy statement, section 2.7). An unrecognised question returns no answer rather than a constructed one, and so does a question about law outside the EU: Praxikon covers only the EU AI Act and the GDPR. For one concrete system or case, the coded assessment tools give a fuller answer.

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": {
      "question": "<question>"
    },
    "name": "answer_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer. Dutch is the default.nl
questionYesThe question in general terms, without names, contact details or identifying numbers.
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
langYes
modeNoscenario, semantic, gdpr, koppeling, out_of_scope (law outside the EU) or none.
viewYes
answerNoThe compact answer, as the published answer endpoint returns it, without the question.
storedNo
messageNo
answeredYes
provenanceYes
alternativesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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. Changed1 schema field changed
    • changedOutput schema / properties / mode / description
      Previous value: -"scenario, semantic, gdpr, koppeling or none."New value: +"scenario, semantic, gdpr, koppeling, out_of_scope (law outside the EU) or none."
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past the annotations: deterministic lookup with no language model, answers come with articles and sources, questions resembling personal data are refused, the question never enters a URL, server log or analytics service, and retention is governed by store_for_improvement with a cited privacy section. It also discloses the failure mode (unrecognised questions return no answer rather than a constructed one), which is exactly the behaviour an agent needs to anticipate.

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 purpose and examples, then routing, then the rewrite requirement, then privacy behaviour — a sensible order with no filler sentences. It is dense and the privacy/retention passage runs long relative to the rest, but every clause carries decision-relevant information.

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?

An output schema exists, so return values need no explanation, and the description still notes that answers include articles and sources. For a read-only, open-world-false lookup with three fully documented parameters, an agent has everything needed: scope, preconditions, failure modes, and privacy handling.

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 the baseline is 3; the description earns a step above by explaining the consequence of the 'question' constraints (a question that looks like personal data is refused) and by tying store_for_improvement to a concrete user request rather than just an optional boolean. It largely restates the retention semantics already present in the schema description, which keeps it from a 5.

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 ('answer a short, general question about the EU AI Act or the GDPR') and immediately grounds it with two concrete examples (chatbot disclosure, DPIA requirement). It also explicitly separates itself from the coded assessment siblings for one concrete system or case, so an agent can pick the right tool without opening a schema.

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?

Gives an explicit when-to-use condition (short, general questions about AI Act/GDPR), explicit exclusions (law outside the EU returns nothing; concrete cases belong to the coded assessment tools), and a mandatory pre-call rewrite step with a length limit. Nothing about selecting this tool versus check_case/classify_system is left to inference.

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