Lexiara

What changed in the corpus

recent_changes

Read-onlyIdempotent

Change feed: provisions added or modified, filterable by jurisdiction, concept and date. detectedAt is when Lexiara observed the change — legal in-force dates come only from the provision itself.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "recent_changes"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum items, default 50.
`since`	No	ISO date: only changes detected after this.
`concept`	No	Restrict to one concept id, e.g. 'eurovoc:4585'.
`jurisdiction`	No	ISO country filter, e.g. 'UK', 'FR', 'EU'.

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

A3.6/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent behavior. The description adds meaningful nuance beyond that: detectedAt reflects when the system observed the change, not the legal in-force date. This helps set expectations about timestamps without contradicting the annotations.

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?

Two sentences, front-loaded with the core purpose and filters, with a single important caveat about detectedAt vs. in-force dates. No filler or redundancy.

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 list operation with a full output schema and all parameters documented, the description communicates the essential behavior and the one subtle timestamp distinction. It could be slightly more complete by naming sibling tools, but nothing critical is missing.

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?

Input schema covers all four parameters with clear descriptions (100% coverage), so the baseline applies. The description reinforces the role of jurisdiction, concept, and date filters but does not add significant new meaning beyond the schema.

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 gives a specific resource (“provisions”) and the nature of the feed (“added or modified”), plus the available filters (“jurisdiction, concept and date”). This is clear enough to orient an agent, though it doesn’t explicitly contrast with siblings like provision_history or follow_updates.

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 guidance on when to choose recent_changes over related tools such as follow_updates, provision_history, or search. The description explains what the tool does but not the context in which it is the right choice.

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?