Skip to main content
Glama

Verify a legal citation

lexatlas_verify
Read-onlyIdempotent

Check one legal citation against the LexAtlas corpus. Call it before quoting or relying on a specific article. Returns: whether the article exists, its status (in force or repealed) together with the date the corpus last checked the official source, provenance (official source and URL), an amendment summary and a confidence level. cite = jur:code:article_no (e.g. ru:gk_rf_1:196, tj:tj_uk:55); if you do not know the code id, call lexatlas_search first. Does not return the article text; use lexatlas_get for that.

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_verify"
  }
}

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)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the description spends its budget on what annotations cannot convey: the exact return payload (existence, in-force/repealed status, last-checked date, provenance URL, amendment summary, confidence) and what is deliberately omitted. With no output schema, this enumeration is the only source of that information.

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?

Front-loaded with the action and the pre-quote trigger; the dense return enumeration is justified because there is no output schema. Minor density cost in the long comma-separated return list, but no sentence is filler.

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?

A read-only verification tool with two params and no output schema — the description covers the trigger, the fallback path, the full result shape, and the boundary with lexatlas_get. Nothing an agent needs in order to call it correctly or interpret the answer 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 schema already defines both parameters and the baseline is 3. The description adds operational meaning for 'cite' beyond the schema by tying an unknown code id to the lexatlas_search fallback. It does not mention the 'lang' parameter's envelope-vs-norm-text nuance, which the schema carries alone.

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?

States a specific verb and resource — 'Check one legal citation against the LexAtlas corpus' — and immediately bounds the scope ('one', 'specific article'). It distinguishes itself from the two nearest siblings by naming lexatlas_search (for code lookup) and lexatlas_get (for article text).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Call it before quoting or relying on a specific article'), an explicit prerequisite workaround ('if you do not know the code id, call lexatlas_search first'), and an explicit exclusion with the correct alternative ('Does not return the article text; use lexatlas_get for that'). No inference is required to route between the three tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.