Skip to main content
Glama
Sign In
LexAPI MCP

LexAPI MCP

Official
by Lex-API
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

lex_recent_documents

Retrieve recently published Official Journal documents. Filter by type, author, language, and look-back window to get a delta over a date range.

Instructions

List documents published to the Official Journal recently. Default window is 7 days. Filterable by document type, author, and language. Use this when the user asks "what was published this week" or wants a delta over a date window.

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

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days.
documentTypeNo
authorNo
languageNoen
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description bears full burden. It states it's a list operation (read-only), default window 7 days, and filterable by type, author, language. Does not disclose if there are rate limits, authentication needs, or what fields are returned.

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: first states purpose, second provides usage tip. No unnecessary words or redundancy. Front-loaded with core function.

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?

Given no output schema, no annotations, and 5 parameters, the description covers basic purpose and filters but omits mention of the limit parameter, return format, and how it relates to other tools (e.g., as a supplement to lex_search). Sufficient for a simple list tool but could be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% (only 'days' has a description). The description mentions default window and filterable options but does not explain the meaning of enum values for documentType, author, language, or the limit parameter. It adds minimal value beyond the schema.

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 clearly states the action (list) and resource (documents published to the Official Journal recently). It distinguishes itself from siblings like lex_search, which is for general search, by focusing on recent publications.

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?

Provides explicit usage context: use when user asks 'what was published this week' or wants a delta over a date window. However, it does not mention when not to use it or explicitly list alternatives.

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

Deploy Server

Other Tools