Skip to main content
Glama

Avokata: Lithuanian law & court practice

Who has cited this (citator)

cited_by
Read-onlyIdempotent

Sign-in required: call connect(email) and connect_verify first (free, one email) unless this connection is already signed in. The citator (citavimo grafas): what has cited this provision (straipsnis) or ruling (nutartis) since: a reverse lookup that full-text search cannot do. Name the subject in ONE of three ways: a ruling by case_no (e3K-3-117-823/2023); a provision by act_number + pinpoint (act_number='CK', pinpoint='6.217'); or any search hit by its document_id (an article id with # needs no pinpoint). A citation string is not a parameter: split it into those parts. These are citations, not endorsements: whether the citing court agreed is not recorded. For citations this document itself makes, use citations_of instead. Example arguments: {"act_number": "CK", "pinpoint": "6.217", "limit": 10}.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many citing edges to return, default 25. `rulings_total` beside the answer is the number of distinct judgments behind it - quote that, not this.
detailNo`compact` (the default) keeps each citing edge's identity, pinpoint, court and date whole and cuts `quote` (the citing sentence) to ~300 characters, with `quote_chars` giving its full length. `full` returns every quote whole.compact
case_noNoThe citator for rulings: pass the case number (e.g. `e3K-3-117-823/2023`) to list later judgments that cite it. Returns only citations strictly after the source decision date (`later_than`). Omit when you already have `document_id`.
includeNoBring back citing rulings left out by default: `cassation_admission` returns the Supreme Court's decisions on whether to accept a cassation appeal (eCIK, CIK, BIK, ATIK numbers), which answer an admission question rather than how the provision or ruling is read. `withheld` says how many were left out.
sessionNoThe `session` value the sign-in returned. Pass it on every call in this conversation, so the sign-in survives however this client handles connections; omit it when the user connected with Sign in (OAuth) or a key.
pinpointNoWhen `document_id` is the act (no `#`), names the article to ask about — `57 straipsnis` or `6.217`. Omit when you already pass a unit id. Same resolution as `read_paragraphs`.
max_charsNoA hard cap on the answer's size in characters, default 15000. Every row is first narrowed (a ~150-character excerpt), then rows are dropped from the end (the lowest-ranked) to fit, and `truncated` says how many and how to get them; data_as_of, notes and caveats are never cut.
act_numberNoAlternative to `document_id` for acts: the register number (`XII-2603`) or a code abbreviation (`DK`, `CK`). Add `pinpoint` to ask about one article. Omit when you pass `case_no` for a ruling citator.
court_levelNoKeep only citing rulings of these court levels (`supreme`, `appeal`, `regional`, `district`, `supreme_administrative`, `regional_administrative`, `constitutional`), counted over every citing ruling held before the list is cut: `supreme` answers 'how has the Supreme Court used this since'.
document_idNoWhat to ask about. An ARTICLE id (search hit `id`, with `#`) answers 'who has applied this article'. A ruling id lists later judgments that cite it. For a ruling citator from a case number, pass `case_no` instead — not both. An act id alone asks about the whole act — or pass the act id with `pinpoint` naming the article. `document.number` (`XIII-2221`) is not an id.
jurisdictionNoWhich jurisdiction the id belongs to (`LT`). Omit for the account's own.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Bring back citing rulings left out by default: `cassation_admission` returns the Supreme Court's decisions on whether to accept a cassation appeal (eCIK, CIK, BIK, ATIK numbers), which answer an admission question rather than how the provision or ruling is read. `withheld` says how many were left out.",
      +  "title": "Include"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / court_level
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Keep only citing rulings of these court levels (`supreme`, `appeal`, `regional`, `district`, `supreme_administrative`, `regional_administrative`, `constitutional`), counted over every citing ruling held before the list is cut: `supreme` answers 'how has the Supreme Court used this since'.",
      +  "title": "Court Level"
      +}
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely new behavioral context: the sign-in flow and free/one-email constraint, the `later_than` temporal semantics, and the crucial caveat 'These are citations, not endorsements: whether the citing court agreed is not recorded' — a limitation an agent would otherwise misinfer. It also notes cassation-admission decisions are excluded by default.

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-loads the auth prerequisite, then the purpose, then the three naming modes, then the caveat, then the example — a sensible order. It is dense and the sign-in sentence is long, but no sentence is filler; slight deduction for density over brevity.

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?

For an 11-parameter, output-schema-less tool with an auth gate, the description covers everything an agent needs to call it correctly: auth, subject forms, temporal direction, exclusion of admission decisions, and the distinction from the sibling. Return shape is largely delegated to the rich per-parameter schema, which is appropriate.

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 a 3 is the baseline, but the description earns above that by explaining the mutual-exclusivity rule across document_id / case_no / act_number+pinpoint and by supplying a worked example. It adds selection logic the schema documents individually but not as a coherent decision.

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 operation on a specific resource — 'what has cited this provision (straipsnis) or ruling (nutartis)' — and frames it as 'a reverse lookup that full-text search cannot do.' It also names the sibling it is not: citations_of, which handles outgoing citations. An agent can distinguish cited_by from citations_of without opening either schema.

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?

Explicitly routes: use citations_of 'for citations this document itself makes,' and it enumerates the three accepted ways to identify the subject (case_no, act_number+pinpoint, document_id), warns 'A citation string is not a parameter: split it into those parts,' and gives a concrete example argument set. Prerequisites (connect/connect_verify) are stated up front with the exception when already signed in.

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.

Resources