Skip to main content
Glama

Lexiara

by org.lexiara
OverviewDiscussionsAdmin

What a provision cites, and what changed it

provision_context
Read-onlyIdempotent

The cross-reference neighbourhood of a provision plus its amendment history. Use this when a provision's relevance is not on its face: a duty that says 'the information referred to in Article 6(1)' is silent about what that information now includes, and about which amending act put it there. Returns citations both ways and the amending acts marked on this provision and on the ones it cites. citedByArticle answers the inbound question at ARTICLE granularity — which provisions of other instruments name THIS article — split into eu and national by the citing instrument's jurisdiction, and distinct from citedBy, which is act-level and returns the same list on every provision of the act.

Lexiara Nexus data requires an API key on a signed-in account. The free plan carries a monthly Nexus allowance; the legislative text itself is always free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eIdYesProvision identifier, e.g. 'art_7__para_1'.
workYesELI of the instrument.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "The JSON response from the corresponding Lexiara API route.",
+  "type": "object"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds material beyond that: the API-key/signed-in-account requirement and the free-plan Nexus allowance, plus a subtle output trait (citedBy returning the same act-level list on every provision).

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?

Purpose and the citedByArticle/citedBy distinction are front-loaded, and the auth note is a compact trailing paragraph. It is somewhat dense and slightly long, but every sentence carries information.

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?

With an output schema present the description need not explain return values, and it still usefully flags the two output fields that are easy to confuse. Combined with the auth disclosure, an agent has enough to call it correctly; the only gap is the absence of explicit sibling routing.

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 description coverage is 100%, so both parameters (eId, work) are already documented. The description adds no syntax, format, or identifier guidance beyond the schema, so the baseline 3 applies.

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?

States a precise verb+resource: 'cross-reference neighbourhood of a provision plus its amendment history', and disambiguates its output concepts (citedByArticle vs citedBy). It does not explicitly contrast itself with closely named siblings such as provision_history or related_works, so an agent must infer the boundary.

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?

Gives a concrete trigger: 'Use this when a provision's relevance is not on its face', with a worked example of a silent cross-reference. It stops short of naming when NOT to use it or routing to alternatives like lookup_provision, but the use condition is clear.

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

All Lexiara toolsInspect
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