Skip to main content
Glama
matematicsolutions

mcp-isap

by matematicsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_actsA

Wyszukiwanie aktow prawa polskiego (Dziennik Ustaw + Monitor Polski) przez oficjalne Sejm ELI API. Pokrycie: 96 000+ aktow od 1918. Filtry: fragment tytulu, rok, publisher (DU/MP), typ aktu, status obowiazywania. Bledy: upstream_error.

get_actA

Pobiera szczegoly aktu po identyfikatorze ELI (np. 'DU/2018/1000' dla Ustawy o ochronie danych osobowych z 2018 r.). Zwraca pelne metadane: tytul, typ, status obowiazywania, wejscie w zycie, slowa kluczowe, linki do tekstu HTML/PDF i strony ISAP.

get_act_textA

Pobiera tekst aktu w formacie HTML (jesli dostepny). Zwraca pierwsze 5000 znakow czystego tekstu (bez tagow) plus link do pelnego HTML/PDF. Uzywaj po get_act zeby ocenic czy akt jest tym, czego szuka uzytkownik.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a distinct purpose: get_act retrieves metadata by ID, get_act_text gets content, and search_acts performs filtered search. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (get_act, get_act_text, search_acts), making it predictable.

Tool Count4/5

Three tools is minimal but appropriate for a focused read-only legal lookup service. Could potentially include more, but the count is reasonable.

Completeness4/5

Covers the core workflow: search, get metadata, get text. Minor gaps like batch operations or version history, but sufficient for the stated purpose.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources