Skip to main content
Glama

Eu Parliament

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Meps

meps
Read-onlyIdempotent

List the Members of the European Parliament sitting NOW, filterable by country and political group. Pass term to query the historical register instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termNoParliamentary term number (e.g. 10 = 2024-2029).
groupNoEP political group. The nine sitting groups are PPE (EPP), S&D, PfE, ECR, Renew, Verts/ALE (Greens), The Left, NI, ESN — pass any of those spellings, or the English name; casing and &/ separators are normalized for you.
limitNo
offsetNo
countryNoMember state — country name ("Ireland"), ISO2 ("IE") or ISO3 ("IRL") all work.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / group / description
      Previous value: -"EP political group acronym (e.g. \"EPP\", \"S&D\", \"RENEW\", \"The Left\")."New value: +"EP political group. The nine sitting groups are PPE (EPP), S&D, PfE, ECR, Renew, Verts/ALE (Greens), The Left, NI, ESN — pass any of those spellings, or the English name; casing and &/ separators are normalized for you."
  2. Changed2 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO 3166-1 alpha-3 (e.g. \"DEU\")."New value: +"Member state — country name (\"Ireland\"), ISO2 (\"IE\") or ISO3 (\"IRL\") all work."
    • changedInput schema / properties / group / description
      Previous value: -"EP political group acronym (e.g. \"EPP\")."New value: +"EP political group acronym (e.g. \"EPP\", \"S&D\", \"RENEW\", \"The Left\")."
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "country": "DEU",
+    "group": "EPP",
+    "term": 10
+  },
+  {
+    "limit": 50,
+    "offset": 0
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "List of MEPs from EU Parliament API",
+  "type": "object"
+}
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context: the temporal distinction between "sitting NOW" and historical data via `term`. No contradictions with 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?

The description is two short, front-loaded sentences. The first sentence states the core purpose and filters; the second clarifies the historical mode. Every word earns its place, with no redundancy or filler.

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 output schema and annotations, the description sufficiently covers the main behaviors: listing current MEPs, filtering by country/group, and switching to historical via term. Pagination parameters (limit/offset) are present in the schema, and the read-only/idempotent nature is annotated. The description is complete for an agent to invoke correctly.

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 60%; term, group, and country have detailed descriptions. The description reinforces `term` as the historical toggle and mentions filterability by country/group, but adds little for `limit` and `offset`. The schema carries most of the parameter meaning, so a baseline 3 is appropriate.

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 specific verb+resource: "List the Members of the European Parliament sitting NOW". It clearly distinguishes the tool's scope (current members) and adds the filter dimensions (country, political group) plus an alternate mode via `term` for historical registers. This strongly differentiates it from the sibling tool `mep` (singular).

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?

The description provides explicit when-to-use guidance: use without `term` for current sitting MEPs, pass `term` for the historical register. It does not explicitly name alternatives like `mep` (singular), but the context is clear enough for an agent to know when this list tool is appropriate.

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

All Eu Parliament toolsInspect
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.

Resources