eu-parliament-mcp-server

Find members of the European Parliament

euparl_search_meps

Read-onlyIdempotent

Find MEPs by name, country, political group, gender, or parliamentary term. Omitted term selects members in office today; explicit term selects that published term roster. Name matching requires every normalized token after case, diacritic, and punctuation normalization over the complete roster before paging. Country and group describe roster context, never voting-date affiliation. Continue with page.next_offset and snapshot; restart at offset 0 without snapshot after snapshot_changed. Read identity and membership history with euparl_get_mep. Empty matches succeed with guidance.

Input Schema

Name	Required	Description
`term`	No	Parliamentary term 0–10; omitted selects members in office today.
`limit`	No	Whole items requested; default 20, effective maximum 100 with notice.
`gender`	No	Supported gender code FEMALE, MALE, NAP, NKN, or NST, case-insensitive.
`offset`	No	Zero-based collection offset; default 0.
`country`	No	Supported ISO alpha-2 country code, case-insensitive; GB maps to historical UK and does not establish current membership. See euparl_list_reference topic mep_filters.
`language`	No	Supported EU ISO-639-1 language, case-insensitive; default en; source text is never translated.
`snapshot`	No	Returned roster snapshot; required for offset above 0, optional at offset 0.
`name_contains`	No	All-token name filter over the complete selected roster; case, diacritics, and punctuation are normalized, without fuzzy scoring.
`political_group`	No	Supported political group code, case-insensitive; accepts EPP, S&D, Verts/ALE, Greens/EFA, The Left, GUE/NGL, Renew, PfE, and Patriots aliases. Query aliases never rewrite historical organization identities. See euparl_list_reference topic mep_filters.

Output Schema

Name	Required	Description
`cap`	No	Effective whole-item page limit.
`page`	No	Whole-item page metadata.
`error`	No	Present when the call failed. Absent on success.
`items`	No	Complete member records on the selected local page.
`shown`	No	Whole items shown on this partial page.
`notice`	No	Publication, language fallback, empty-result or continuation guidance.
`available`	No	Whether the selected source array was published, including a published empty array.
`truncated`	No	True when this page returns only part of the selected collection.
`totalCount`	No	Exact count only when published or computed over a complete collection.
`appliedFilters`	No	Actual normalized retrieval scope and filters.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses important operational behavior: snapshot-based paging, restart behavior after snapshot_changed, complete-roster name matching before paging, and empty-match success with guidance. It also clarifies that country and group are roster context, not voting-date affiliation.

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?

The description is dense but front-loaded and purpose-first, with no wasted filler. Each clause carries operational meaning relevant to a nine-parameter search tool.

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?

Given the nine parameters, existing output schema, and safe read-only annotations, the description covers the remaining decision-relevant behavior: filtering scope, term semantics, pagination/snapshot handling, empty results, and when to use the detail sibling. Nothing essential for correct invocation appears 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 description coverage is 100%, so the schema already documents all nine parameters and the baseline is 3. The description adds useful semantic context around term omission, name-token normalization, roster-context filtering, and snapshot continuation, though it does not add meaning for every parameter beyond the schema.

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 uses a clear verb-resource pair, 'Find MEPs', and lists the supported filters, making the tool's purpose immediately identifiable. It also distinguishes the lookup role from the detail-oriented sibling by saying to read identity and membership history with euparl_get_mep.

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?

It explicitly explains how term omission versus explicit term selection behaves, how name matching works, and how country/group filters should be interpreted. It also directs agents to the appropriate sibling for identity/history and gives a clear rule for pagination continuation versus restart after a snapshot change.

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

All eu-parliament-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.