Lexiara

Provisions tagged with a concept

provisions_by_concept

Read-onlyIdempotent

Cross-jurisdiction view of one legal concept: every provision tagged with the given EuroVoc concept, with tagging method and confidence. E.g. 'eurovoc:4585' (VAT), 'eurovoc:4392' (VAT rate). The language-neutral way to line up EU and national law on the same subject.

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": {
      "conceptId": "<conceptId>"
    },
    "name": "provisions_by_concept"
  }
}

Input Schema

Name	Required	Description
`conceptId`	Yes	Namespaced concept id, e.g. 'eurovoc:4585'.
`jurisdiction`	No	ISO country filter, e.g. 'UK', 'FR', 'EU'.
`minConfidence`	No	Drop tags below this confidence (0-1).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The JSON response from the corresponding Lexiara API route.",
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the readOnly annotations, the description explains the actual behavior: it returns all tagged provisions across jurisdictions and includes tagging method and confidence. This gives agents useful expectations about result content and scope, though it does not discuss limits or pagination.

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?

The description is concise, front-loads the core behavior, and uses examples effectively without verbosity. Each sentence adds value: definition, example, and use-case rationale.

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 read-only listing tool with a rich output schema and clear annotations, the description is nearly complete. It explains the concept-centric scope and cross-jurisdiction nature, but it does not explicitly mention whether there are pagination or size limits on results, which would be useful for an agent querying broadly.

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?

The input schema already covers all three parameters at 100% coverage gift, and the description adds meaningful context with concrete concept ID examples)Skip. It does not add much semantic detail for jurisdiction or confidence filtering beyond the schema descriptions, but the example and language-neutral framing strengthen conceptId.

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 names a specific operation (cross-jurisdiction view of provisions by EuroVoc concept) and clearly explains what the tool returns: every provision tagged with the given concept, including tagging method and confidence. The examples ('eurovoc:4585', 'eurovoc:4392') anchor the concept and help distinguish it from more general search and definition tools.

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?

The description provides clear context for when this tool is appropriate: when you need a language-neutral way to line up EU and national law on the same legal concept. It does not explicitly name alternative siblings or state when not to use it, which keeps it from a 5.

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

All Lexiara tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?