TAAP MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TAAP_BASE_URL | No | Base URL of the data.gov.lt open-data API. | https://get.data.gov.lt |
| TAAP_AUDIT_DIR | No | Directory where the audit log is written. | ~/.taap-mcp/audit |
| TAAP_CACHE_DIR | No | Directory used for the response cache. | ~/.taap-mcp/cache |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lt_searchB | Search Lithuanian acts by title (case-insensitive) with optional filters. |
| lt_get_actB | Fetch Lithuanian act metadata by its TAR code, incl. validity and issuer fields. |
| lt_coverageA | Declare what this connector covers, how it is sourced, and what it does NOT cover. Call this before telling a user that the law "does not contain" something, and whenever a search comes back empty: the absence may be a gap in this connector rather than in the law. Every gap carries a fallback saying where to look instead. Returns:
|
| lt_get_textA | Fetch the full Lithuanian text of an act by its TAR code - the version in force today. Returns the consolidated edition (suvestine redakcija) in force today when the source has
one; otherwise the newest consolidated edition flagged |
| lt_list_editionsA | List the consolidated editions (suvestines redakcijos) of an act, newest first. |
| lt_get_edition_textA | Fetch the consolidated text of an act in force on a date, or a specific edition. |
| lt_list_attachmentsB | List the attachments (priedai) of an act. |
| lt_get_attachmentA | Fetch one attachment (priedas) of an act: extracted text, metadata and download URL. |
| lt_get_provisionsA | List the provisions of an act (its structure) with stable ids and references. Laws: chapters, articles ( |
| lt_get_provisionA | Fetch one provision of an act by reference, with its full text and a ready citation. |
| lt_resolve_referenceA | Resolve a citation of an act, as written in a document, to TAR acts - and check it. Documents cite acts by number and date ("2000 m. sausio 11 d. įstatymas Nr. VIII-1524"),
not by TAR code. Official numbers are not unique, so every candidate is returned with the
checks made: number / date / type / title match and whether it was in force on |
| lt_search_in_actB | Find the provisions of one act whose wording contains a phrase. |
| lt_get_definitionsA | List the terms an act defines (its "sąvokos" article or point) with provision ids. |
| lt_list_amendmentsA | List the acts that amended an act and which provisions each one changed. |
| lt_diff_editionsA | Compare the provisions of an act between two dates (two consolidated editions). |
| lt_healthA | Check whether data.gov.lt answers right now, and how the local cache looks. Call it when a tool returns Returns:
|
| lt_check_document_referencesA | Find every act and provision a Lithuanian document cites and check each against TAR. Recognises acts cited with number and date ("Lietuvos Respublikos Vyriausybės 2007 m. rugpjūčio 22 d. nutarimu Nr. 875"), laws and codes cited by name ("Civilinio kodekso"), short names the document defines ("(toliau - Taisyklės)") and provisions of those acts ("Įstatymo 5 straipsnio 2 dalis", "Taisyklių 24.1 papunktis", "45.1-45.3 papunkčiuose"). |
| lt_search_court_rulingsB | Search Constitutional Court (Konstitucinis Teismas) acts registered in TAR, newest first. |
| lt_get_court_rulingB | Fetch a Constitutional Court act with its parts split out. |
| lt_find_rulings_on_actA | Constitutional Court acts on a given act (optionally one provision), with their outcome. Matches KT titles ("Dėl ... civilinio kodekso 4.84 straipsnio 7 dalies ... atitikties
Lietuvos Respublikos Konstitucijai") against the act's current and former titles, or - for
subordinate acts - its date and number. With |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Most tools target distinct resource/action pairs, but there is some overlap among text and structure retrieval tools: lt_get_text, lt_get_edition_text, lt_get_provisions, lt_get_provision, and lt_get_definitions all deal with act content and could be briefly confused. The detailed descriptions generally resolve the boundaries, and reference tools lt_resolve_reference and lt_check_document_references are distinguishable by scope.
All tools use a consistent lt_ prefix and snake_case, with mostly verb_noun patterns such as lt_get_act, lt_search_in_act, and lt_list_amendments. The main deviations are noun-style names lt_coverage and lt_health, which are minor but slightly break the otherwise predictable convention.
At 20 tools this is somewhat above the ideal compact range, but the legal-research domain legitimately requires separate operations for acts, provisions, editions, amendments, attachments, court rulings, references, and health/coverage checks. No tool appears clearly redundant or filler, so the set is slightly heavy but reasonably scoped.
The surface covers core legal retrieval and lifecycle needs: search, act metadata, full text, provision structure, editions, diffs, amendments, attachments, court rulings, citation checks, and connector coverage/health. A notable possible gap is cross-act full-text search, since lt_search appears title-based and lt_search_in_act is limited to a single act, but most workflows are well supported.