Skip to main content
Glama

Fedlex Connector

by ch.fedlex-connector

get_law_text

Retrieve the official consolidated text of a Swiss federal act (or a specific title/chapter) directly from Fedlex (fedlex.admin.ch). This is the PRIMARY tool for answering Swiss law questions — always start here. Fetch the full act or a specific section, then locate relevant provisions in the returned text. Prefer this over get_article unless you already know the exact article number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for paginated results (default: 1). Large acts are split across multiple pages.
sectionNoLimit to a specific title, chapter, or part (e.g. 'Titre huitième', 'Zweiter Teil'). If omitted, returns the full act.
languageNoLanguage (default: de)
rs_numberYesRS/SR number (e.g. '210' for CC, '220' for CO)

TDQS

A4.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, and description does not disclose behavioral traits like read-only nature, error handling, or what happens with invalid RS numbers. It focuses on usage rather than behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise with two main sentences and a usage hint, but could be slightly more structured to separate behavior from usage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a text retrieval tool with no output schema, it covers when to use, parameter details, and pagination, though it does not specify the output format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 4 parameters have schema descriptions, and the description adds value by explaining pagination (page parameter), giving examples for section, and noting language default.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves official consolidated Swiss federal law text from Fedlex, and explicitly distinguishes it from siblings like get_article by advising preference unless exact article known.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance: 'always start here', 'Prefer this over get_article unless you already know the exact article number', and mentions pagination for large acts.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Fedlex Connector toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool has a clear, non-overlapping purpose: fetching specific articles, retrieving full law text, listing consolidation dates, and searching by title. No ambiguity.

Naming Consistency5/5

All tools follow a consistent lowercase verb_noun pattern (get_article, get_law_text, list_amendments, search_by_title), making them easy to understand and remember.

Tool Count5/5

With 4 tools, the server is well-scoped for its purpose of accessing Swiss federal legislation. Each tool provides essential functionality without redundancy.

Completeness4/5

The tools cover finding a law by title, retrieving full text, accessing specific articles, and listing version dates. A minor gap is the lack of article content search, but descriptions guide agents to use get_law_text for that.

Resources