Skip to main content
Glama
nulegal-startup

recht-mcp

by nulegal-startup
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Recent changes

getChanges
Read-onlyIdempotent

Check which legal provisions received new text recently, sorted newest first. Poll with a 'since' date to see changes you haven't processed yet.

Instructions

Which provisions got a new text recently, newest first — the freshness feed, as JSON. Poll it with since set to the newest observed you have already processed.

observed is the day the new text was FIRST SEEN here, which is not necessarily the day it came into force. Say so if you report a date. The window is the last 120 days; the law's own Änderungsverlauf goes further back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
sinceNoOnly changes observed on or after this date.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds valuable semantics: `observed` is first-seen date, not in-force date, and warns to say so when reporting. This contextual nuance goes beyond the annotations.

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

Conciseness5/5

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

Two tight paragraphs: the first gives purpose and usage in one sentence; the second adds necessary nuance about the date semantics and window. No filler; front-loaded with the core action.

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

Completeness5/5

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

For a read-only feed with two optional parameters, the description covers purpose, polling behavior, date semantics, and limits. An agent can correctly invoke it without further information; output format is noted as JSON, which is sufficient.

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?

The schema documents `since` with a pattern and description, and `limit` with defaults. The description enriches `since` by defining what 'observed' means and clarifies the recency ordering. With 50% schema coverage, the description compensates meaningfully.

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 returns provisions with recently changed text, ordered newest first, as a JSON freshness feed. This is a specific verb-resource-action combination that distinguishes it from siblings like search or getNorm.

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?

Explicit polling guidance is provided: set `since` to the newest observed value already processed. It also notes the 120-day window and contrasts with the law's own Änderungsverlauf, implying alternatives for older data, though it doesn't name the specific sibling tool.

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