Skip to main content
Glama

Search parliamentary speeches (Amtliches Bulletin)

search_parliament_speeches
Read-only

Search Swiss parliamentary speeches by speaker, keyword, date, or session to retrieve excerpts, debate context, and official Bulletin links.

Instructions

Search the verbatim record of speeches in the National Council and Council of States (Amtliches Bulletin transcripts) by speaker and/or keyword, optionally within a date range or session. Returns speaker, function, parliamentary group, canton, council, date, the business debated (short number + title when resolvable), a plain-text excerpt centred on the keyword, and a link to the official Bulletin debate. Keyword matching is case-sensitive and matches the speech's original language (e.g. 'Klimaschutz', 'Neutralität', 'intelligence artificielle'). Examples: {speaker:'Noser', keyword:'Datenschutz'}; {keyword:'Kita', date_from:'2024-01-01'}; {person_number:4057}. Speaker names come from search_council_members.

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": "search_parliament_speeches"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
date_toNoLatest meeting date, YYYY-MM-DD
keywordNoCase-sensitive word/phrase in the speech text, in the language it was spoken, e.g. 'Klimaschutz'
speakerNoFragment of the speaker's full name, e.g. 'Noser', 'Funiciello'
languageNoLanguage of labels such as council name (speech text stays in its original language)DE
date_fromNoEarliest meeting date, YYYY-MM-DD
session_idNoSession ID from get_session_schedule (field ID)
excerpt_charsNoMax characters of speech text per result
person_numberNoExact PersonNumber of a council member (from search_council_members ID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safe-read profile (readOnlyHint, openWorldHint), and the description still adds real behavioral detail: keyword matching is case-sensitive and applies to the original spoken language, excerpt_chars caps returned text, and the business field is only populated 'when resolvable'. It does not mention rate limits or pagination behavior, which keeps it at a 4.

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?

Front-loaded with the core purpose, then return fields, then the case-sensitivity caveat, then examples — a sensible order with no filler. The prose is somewhat dense in a single block, so slightly less scannable than an ideal definition, but every sentence carries information.

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 9-parameter, zero-required search tool with no output schema, the description enumerates the returned fields (speaker, function, group, canton, council, date, business, excerpt, official link) and explains the two behavioral gotchas (case-sensitive original-language matching, resolvability of business). Nothing an agent needs to call it correctly is missing.

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 already 89%, so the baseline is 3, but the description adds derivation guidance the schema cannot: speaker names come from search_council_members and person_number takes that tool's ID, while session_id comes from get_session_schedule. It also clarifies that the language parameter affects labels only, not the speech text, disambiguating a parameter whose schema note is easy to misread.

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?

States a specific verb and resource ('Search the verbatim record of speeches in the National Council and Council of States (Amtliches Bulletin transcripts)') plus the filtering axes (speaker, keyword, date range, session). This clearly separates it from sibling tools like search_parliament_business, which searches business items rather than speech transcripts.

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?

Gives three concrete usage patterns ({speaker+keyword}, {keyword+date_from}, {person_number}) and routes the agent to search_council_members for speaker names and get_session_schedule for session_id. It lacks an explicit 'use X instead when' exclusion, so it falls short of a 5, but the context is clear enough to select the tool confidently.

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