Skip to main content
Glama
metaneutrons

German Legal MCP Server

by metaneutrons

dip:search_plenarprotokoll

Search German parliamentary debate transcripts using full-text queries to find discussions on specific topics, legislative periods, or dates.

Instructions

Search Plenarprotokolle (parliamentary debate transcripts) with full text search. Returns protocols where the search term appears in the debate text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesFull text search query (e.g., "Urheberrecht", "UrhDaG")
wahlperiodeNoLegislative period (e.g., 20, 21)
herausgeberNoBT = Bundestag, BR = Bundesrat
date_startNoStart date (YYYY-MM-DD)
date_endNoEnd date (YYYY-MM-DD)
limitYesMax results (default: 10)

Implementation Reference

  • The main handler function that executes the dip:search_plenarprotokoll tool logic.
    export async function handleSearchPlenarprotokoll(client: DipClient, args: Record<string, unknown>): Promise<ToolResult> {
      const { query, wahlperiode, herausgeber, date_start, date_end, limit = 10 } = args as {
        query: string; wahlperiode?: number; herausgeber?: string;
        date_start?: string; date_end?: string; limit?: number;
      };
    
      const params: Record<string, string | number> = { 'f.text': query, rows: limit };
      if (wahlperiode) params['f.wahlperiode'] = wahlperiode;
      if (herausgeber) params['f.herausgeber'] = herausgeber;
      if (date_start) params['f.datum.start'] = date_start;
      if (date_end) params['f.datum.end'] = date_end;
    
      const result = await client.searchPlenarprotokollText(params);
      const text = `${result.numFound} Protokolle\n\n${result.documents.map(formatProtokoll).join('\n\n---\n\n')}`;
      return { content: [{ type: 'text', text }] };
    }
  • Tool definition and registration schema for dip:search_plenarprotokoll.
      description:
        'Search legislative processes (Vorgänge) in DIP. Returns Gesetzgebungsvorgänge with status and linked Drucksachen-Nummern. ' +
        'Useful for tracking a law through the legislative process or finding all related documents.',
      inputSchema: z.object({
        query: z.string().describe('Search keyword (matched against title)'),
        vorgangstyp: z.string().optional().describe('Type filter: "Gesetzgebung", "Schriftliche Frage", "EU-Vorlage", etc.'),
        wahlperiode: z.number().optional().describe('Legislative period (e.g., 20, 21)'),
        date_start: z.string().optional().describe('Start date (YYYY-MM-DD)'),
        date_end: z.string().optional().describe('End date (YYYY-MM-DD)'),
        limit: z.number().optional().default(10).describe('Max results (default: 10)'),
      }),
    },
    {
      name: 'dip:search_plenarprotokoll',
      description:
        'Search Plenarprotokolle (parliamentary debate transcripts) with full text search. ' +
Behavior3/5

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

Since no annotations exist, description carries full burden. It adds valuable matching logic ('search term appears in the debate text') and return value disclosure ('Returns protocols'). However, it omits safety confirmation (read-only status), rate limits, or pagination behavior that annotations would typically provide.

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 sentences with zero waste: first defines action and resource, second defines return behavior. Front-loaded with the most critical information (what is being searched) and appropriate length for the tool complexity.

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 100% schema coverage and no output schema, the description adequately covers the tool's purpose and return type. Minor deduction for not explicitly stating read-only/safety characteristics given the absence of annotations, though this is implied by 'Search' and 'Returns'.

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

Parameters3/5

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

Schema description coverage is 100%, establishing baseline 3. Description adds 'full text search' context for the query parameter but does not elaborate on specific parameter semantics (e.g., that 'herausgeber' filters by chamber) beyond what the schema already provides.

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?

Excellent clarity: specific verb 'Search' + resource 'Plenarprotokolle (parliamentary debate transcripts)' + method 'full text search'. Distinguishes from sibling tools like dip:search and dip:search_vorgang by explicitly specifying the parliamentary debate transcript domain.

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

Usage Guidelines3/5

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

Provides implied usage context (use when searching debate text), but lacks explicit guidance on when to choose this over dip:search (general) or dip:search_vorgang (legislative procedures). No exclusions or prerequisites mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/metaneutrons/german-legal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server