Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TK_MCP_AUDIT_DIRNoOverride the audit log directory (default is ~/.matematic/audit/tk-mcp.jsonl).

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

CapabilityDetails
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

NameDescription
search_judgmentsA

Szuka orzeczen TK w wyszukiwarce trybunal.gov.pl (Solr, type=7383).

Zwraca globalny count z naglowka i jedna strone wynikow. Brak naglowka licznika albo licznik 0 to count=0 z pustymi items - nie blad.

get_judgment_textA

Pelny tekst orzeczenia TK ze strony trybunal.gov.pl.

Parser scope'uje sie do kontenera #content (nav/naglowek emituja wlasne dlugie <p>), wiec zwrocone akapity to sklad orzekajacy i uzasadnienie, bez boilerplate. Bez PDF, bez JS.

tk_coverageA

Declare what this connector covers, how it is sourced, and what it does NOT cover.

Call this before telling a user that the Constitutional Tribunal record "does not contain" something, and whenever a search comes back empty: the absence may be a gap in this connector rather than in the TK record. Every gap carries a fallback saying where to look instead.

Returns: Coverage with families, an as-of note, and a non-empty list of known gaps.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation5/5

search_judgments (find judgments) and get_judgment_text (fetch full text of a known judgment) target clearly different actions, and tk_coverage is an explicit meta/coverage declaration tool that plays a distinct role. No overlap or plausible misselection.

Naming Consistency4/5

search_judgments and get_judgment_text follow a clean snake_case verb_noun pattern. tk_coverage breaks it by using a namespace prefix and no verb, but it is still readable and only a single deviation.

Tool Count4/5

Three tools is lean for a read-only judgment connector but each earns its place: search, retrieve, and a coverage/gap disclaimer. Slightly thin but well-scoped rather than padded.

Completeness4/5

The core read lifecycle (search then fetch full text) plus a coverage/gap declaration is covered for this domain. Minor gaps remain around pagination beyond one page and metadata-only listing, which the coverage tool at least documents.

Maintenance

ActivityMaintained
ResponsivenessNo issues