Skip to main content
Glama

Lex: Luxembourg Law MCP Server

ask

The assistant, switched on as a labelled preview: the question, with obvious identifiers masked by code, is sent to the configured processor, which only plans which operations to run; code runs them, decides the verdict and writes every sentence from fixed wording; the answer is an answer_dossier (or the refusal advice_boundary), and a question it cannot answer gets assistant_v3_unavailable.

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": "ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses meaningful behavior: obvious identifiers are masked by code, the configured processor only plans operations while code executes them and decides the verdict, every sentence is written from fixed wording, and the output is an answer_dossier or refusal/unavailable outcome. It does not mention auth or rate limits, but it is unusually transparent about the processing pipeline and deterministic output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense sentence with semicolons and specialized terms, making it hard to parse. It is not front-loaded with a clear statement of purpose and forces the reader to untangle the architecture before understanding what the tool does.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema and no annotations, the description explains the processing model and the possible output categories reasonably well. However, it omits usage guidance and does not describe the structure or contents of answer_dossier, leaving gaps for an agent trying to invoke it confidently.

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 coverage is 0% for the single required question parameter. The description adds relevant meaning by noting that obvious identifiers in the question are masked by code, but it does not clarify the expected question format, length, or examples beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description conveys that this is a question-answering tool with a preview assistant, masked identifiers, and outputs such as answer_dossier, advice_boundary, or assistant_v3_unavailable. However, the purpose is buried in architecture jargon and it never plainly states 'ask a question' or differentiates itself from siblings like dossier or search.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives such as dossier, search, or answer_drift. The description only implies that it handles questions and has a refusal/unavailable path, but gives no conditions or exclusions.

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