Skip to main content
Glama

Recent changes to federal legislation

list_recent_legislation_changes
Read-only

Find Swiss federal law changes within a date range: amendments, entries into force, or repeals, with dates, SR numbers, titles, and Fedlex links. Use future dates to see scheduled changes.

Instructions

What changed in Swiss federal law in a date range (Classified Compilation): 'amended' = acts for which a new consolidated version became applicable (amendments taking effect, incl. new acts), 'entered_into_force' = acts that entered into force, 'repealed' = acts that ceased to be in force. Returns date, SR number, title and Fedlex link, newest first. Dates may lie in the future to see scheduled changes. Examples: {} (amendments in the last 30 days); {change:'entered_into_force', date_from:'2025-01-01', date_to:'2025-01-31'}; {sr_prefix:'8', query:'Kranken'} (health law).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_recent_legislation_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoOptional title keyword in the chosen language
changeNoamended
date_toNoEnd date YYYY-MM-DD (default: today)
languageNode
date_fromNoStart date YYYY-MM-DD (default: 30 days ago)
sr_prefixNoRestrict to an SR area, e.g. '2' (private law), '6' (finance/tax), '8' (health/labour), '0.' (treaties)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint, but the description adds substantial behavior on top: the exact return fields (date, SR number, title, Fedlex link), newest-first ordering, and default date windows (30 days back to today). The per-category definitions of 'amended', 'entered_into_force' and 'repealed' disambiguate results in a way neither annotations nor schema do.

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?

The description is front-loaded with purpose, then semantics of the enum, then return shape, then three compact example invocations — every block earns its place. It is a single dense paragraph, so the shift from definitions to examples is slightly harder to scan than it could be.

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?

With seven optional parameters and no output schema, the description supplies the return fields, ordering, and default date behavior an agent needs to call it blind. The only omissions are the language and limit parameters, whose meanings are obvious from their names and schema defaults.

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?

Schema coverage is 57%, and the description compensates well for the ambiguous parts: it explains what each 'change' enum value actually means, gives an SR area example ('8' for health/labour via the Kranken query example), and clarifies that dates may be in the future. The 'language' and 'limit' parameters are left entirely to the schema, which holds it back from a 5.

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

Purpose4/5

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

The description opens with a specific framing ('What changed in Swiss federal law in a date range (Classified Compilation)') that clearly separates this change-feed tool from a plain law-text search, and it spells out the three change categories. It never names a sibling tool (e.g. search_federal_law) to reinforce the boundary, so differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

It gives concrete when-to-use signals: an empty call yields amendments in the last 30 days, a date range with change:'entered_into_force' filters by type, and sr_prefix plus query targets an area like health law. It also notes that future dates surface scheduled changes, which is a real usage hint. No explicit exclusions or 'use X instead' guidance is provided.

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

Deploy Server

Other Tools