Skip to main content
Glama
Sign In

LexAtlas

by app.creatora.lexatlas
OverviewDiscussionsAdmin

Get article text

lexatlas_get
Read-onlyIdempotent

Full text of one article with its act, status, the date the corpus last checked the source, and provenance. Call it when you need the exact wording to quote. as_of=YYYY-MM-DD returns the wording in force on that date, reconstructed from the amendments with the amending law named (Russian codes). The norm text is always in its official language; lang only sets the language of the metadata. Also lists norms linked through the citation graph.

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": {
      "cite": "<cite>"
    },
    "name": "lexatlas_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
citeYesjur:code:article_no, e.g. ru:gk_rf_1:196 or tj:tj_uk:55
langNolanguage of the metadata envelope (not of the norm text)
as_ofNoYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish the safe-read profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds real behavior: as_of reconstructs in-force wording from amendments with the amending law named, and norm text is always in the official language regardless of lang. It omits things like size/length limits of the returned text or error behavior for unknown cites.

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?

Front-loaded with the return payload, then usage trigger, then the two parameter behaviors, then the citation-graph extra. Five sentences, no filler, and each one changes how an agent would call the tool.

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

Completeness5/5

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

With three parameters, full schema coverage and no output schema, the description carries the burden of describing returns and does: article text, act, status, source-check date, provenance, plus linked norms. Nothing needed to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond it: it explains what as_of actually does (reconstructs the version in force, names the amending law) and clarifies that norm text is never translated while lang only affects metadata. The cite format itself is left entirely to 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?

A specific verb-and-resource statement: it returns the full text of ONE article plus its act, status, source-check date and provenance, and additionally the linked norms from the citation graph. The phrase 'Call it when you need the exact wording to quote' separates it from the search/related/verify siblings without needing their schemas.

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?

'Call it when you need the exact wording to quote' gives a clear selection trigger, and the as_of sentence explains the historical-retrieval use case. It stops short of naming an alternative tool or a when-not-to-use condition, so it is clear but not exhaustive.

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

All LexAtlas 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