Skip to main content
Glama
matematicsolutions

at-eli-mcp

by matematicsolutions
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AT_ELI_BASE_URLNoBase URL for the RIS APIhttps://data.bka.gv.at/ris/api/v2.6
AT_ELI_AUDIT_DIRNoDirectory for audit logs~/.matematic/audit
AT_ELI_CACHE_DIRNoDirectory for caching responses~/.matematic/cache/at-eli

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
at_searchA

Search Austrian federal law (RIS Bundesrecht).

Maps to GET /Bundesrecht. Each hit gets eli_uri, human_readable_citation, source_url and content_urls (html/xml).

at_get_textB

Fetch the full text of an act from a RIS content URL.

at_case_searchA

Search Austrian case law (RIS Judikatur).

Maps to GET /Judikatur. Each hit gets a native ecli, human_readable_citation, source_url and content_urls (html/xml).

at_get_case_textA

Fetch the full text of a decision from a RIS content URL.

at_list_collectionsA

List the RIS collections and which are exposed by this connector.

Returns: List of Collection (code, name, note).

at_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: 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

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/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: listing collections, searching legislation, fetching legislation text, searching case law, fetching case law text, and declaring coverage. There is no meaningful overlap or ambiguity between tools.

Naming Consistency4/5

Names mostly follow a consistent at_ + verb + noun pattern, e.g. at_list_collections, at_get_text, at_get_case_text. Minor deviations exist, such as at_search being generic compared to at_case_search, but the pattern remains readable and predictable.

Tool Count5/5

Six tools is a well-scoped set for a legal research connector covering both legislation and case law. Each tool earns its place, and the count is neither thin nor bloated.

Completeness5/5

The tool surface covers the full lifecycle of the domain: discover collections, search both law and cases, retrieve full texts, and understand coverage gaps. The explicit coverage tool addresses a common failure mode and makes the set feel complete for its stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources