Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CH_ELI_BASE_URLNoSPARQL endpoint URLhttps://fedlex.data.admin.ch/sparqlendpoint
CH_ELI_AUDIT_DIRNoAudit directory~/.matematic/audit
CH_ELI_CACHE_DIRNoCache directory~/.matematic/cache/ch-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
ch_search_actsA

Full-text search over Swiss federal act titles.

ch_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.

ch_get_actA

Fetch full detail for one Swiss federal act by its Fedlex ELI URI.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: searching act titles, fetching an act by ELI URI, and declaring coverage/gaps. There is no meaningful overlap between them.

Naming Consistency4/5

The ch_ prefix is consistent and data operations follow a verb_noun pattern: ch_search_acts and ch_get_act. ch_coverage deviates slightly by being a noun-only name, but the pattern is still readable and predictable.

Tool Count4/5

Three tools is lean but reasonable for a narrowly scoped legal retrieval connector. The count is slightly small, but each tool contributes a distinct capability rather than padding the surface.

Completeness3/5

The connector covers the essential search-and-fetch workflow for Swiss federal acts, and the explicit coverage tool helps surface gaps. However, the surface is minimal and lacks obvious conveniences such as browsing by family or fetching act versions, so some workflows will still require fallback to external sources.

Maintenance

ActivityMaintained
ResponsivenessNo issues