Skip to main content
Glama

Related norms (citation graph)

lexatlas_related
Read-onlyIdempotent

Norms linked to one article through the citation graph, with the meaning of each link (refers_to, except, amends, repeals, applies_by_analogy, implements, ratifies, conflicts_with, lex_specialis, supranational_basis) and the kind of target. Call it to find exceptions, special rules and amending acts around a norm. cite = jur:code:article_no; direction = in|out|both (default both); limit 1-50 (default 10).

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

Input Schema

NameRequiredDescriptionDefault
citeYesjur:code:article_no, e.g. ru:gk_rf_1:196 or tj:tj_uk:55
limitNo
directionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world=false, so the safety profile is settled. The description adds genuine behavioral context beyond that: the traversal is confined to the citation graph, each edge carries one of ten named relations plus a target kind, and direction/limit defaults shape the result set.

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?

The output shape, the usage trigger and the parameter constraints are each packed into one sentence each with no filler. Slightly dense parameter listing, but front-loaded and every clause earns its place.

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?

With no output schema, the description takes on the burden of describing returns and does so (link meaning plus target kind). An agent has everything needed to call it correctly; only explicit sibling routing is absent.

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

Parameters5/5

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

Schema coverage is only 33% (only cite is documented), so the description must carry the rest — and it does: cite format as jur:code:article_no, direction's in/out/both values with default both, and limit's 1-50 range with default 10. That fully compensates for the schema gap.

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 first sentence names the exact resource (norms linked to one article via the citation graph) and enumerates the link semantics returned, which is far more specific than a generic 'get related'. An agent can distinguish this from lexatlas_get or lexatlas_search, though no sibling is named explicitly.

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 to find exceptions, special rules and amending acts around a norm' supplies a concrete trigger for invocation. There is clear positive guidance but no explicit when-not or named alternative such as lexatlas_get.

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.