Skip to main content
Glama

Search legal norms

lexatlas_search
Read-onlyIdempotent

Find norms by meaning or by keywords across jurisdictions and languages (full-text plus semantic search). Call it when you have a legal question but no exact citation, then pass the returned cite ids to lexatlas_verify or lexatlas_get. query needs at least 2 characters including a letter or digit. jur narrows the search; regional jurisdictions (e.g. ru-mow, Moscow) are searched only when named in jur. k = number of results, default 8. Returns cite ids, titles, snippets and status.

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": {
      "query": "<query>"
    },
    "name": "lexatlas_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNonumber of results, default 8
jurNocomma-separated jurisdiction codes, e.g. ru,kz
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the minimum query constraint (2 characters including a letter or digit) and the non-obvious scoping rule that regional jurisdictions such as ru-mow are only searched when named in jur. It also lists the returned fields (cite ids, titles, snippets, status), which annotations do not cover. Ranking behavior and any limits on result quality are not explained, keeping it below a 5.

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?

Five dense sentences, front-loaded with purpose and trigger, then constraints, then return values. Nothing is redundant with the title or with the schema beyond the harmless 'k' default restatement.

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, non-destructive search with no output schema, the description covers when to call it, parameter constraints, one subtle scoping rule, and the shape of the response. Only ranking/relevance behavior when both keyword and semantic search apply is left unstated.

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 67% and the undescribed required parameter 'query' is covered in the description via its length/character constraint. The 'jur' parameter gains real meaning from the note that regional jurisdictions must be named explicitly, and 'k' just repeats the schema default of 8.

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 ("Find norms") plus the two search modes (full-text and semantic) and the cross-jurisdiction/language scope. It also distinguishes itself from siblings by positioning its output as input to lexatlas_verify or lexatlas_get.

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?

"Call it when you have a legal question but no exact citation" gives an explicit trigger condition, and the follow-on instruction to pass cite ids to lexatlas_verify or lexatlas_get routes the agent through the correct workflow. No alternative is left ambiguous.

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.