sweden-parliament-mcp-server

Read parliamentary member

riksdag_get_member

Read-onlyIdempotent

Read one member register entry and assignment history by exact member ID. Assignment dates preserve source precision and do not establish historical sitting status.

Input Schema

Name	Required	Description
`memberId`	Yes	Numeric memberId from riksdag_search_members, including leading zeros.
`revision`	No	Revision returned by the preceding assignment page.
`assignmentLimit`	No	Requested assignments; applied maximum 100.
`assignmentOffset`	No	Assignment offset in published source order.

Output Schema

Name	Required	Description
`name`	No	Published given and family names, when present.
`error`	No	Present when the call failed. Absent on success.
`found`	No	Whether the exact member IID exists.
`party`	No	Published party code.
`source`	No	Required attribution to the Swedish Parliament.
`status`	No	Unmodified source service-status label.
`hasMore`	No	Whether assignments remain.
`notices`	No	All applicable notices, including an empty list.
`guidance`	No	Next step when the member IID is absent.
`memberId`	No	Numeric register IID, including leading zeros; absent for some historical and European Parliament entries.
`nextCall`	No	Complete next-assignment call.
`revision`	No	Complete normalized member record revision.
`givenName`	No	Published given name.
`sourceUrl`	No	Public register source URL.
`truncated`	No	Whether further assignments remain available through nextCall.
`familyName`	No	Published family name.
`assignments`	No	Published assignments in source order.
`retrievedAt`	No	Source fetch time, retained unchanged on cache hits.
`constituency`	No	Published constituency label.
`returnedCount`	No	Assignments returned on this page.
`upstreamQuery`	No	Upstream query echo; not proof that a filter was applied.
`effectiveQuery`	No	Deterministic normalized input, applied defaults and local filters.
`sourceRecordId`	No	Source register UUID, distinct from the member IID.
`assignmentLimit`	No	Applied assignment limit.
`assignmentTotal`	No	Exact total published assignments.
`detailAvailable`	No	Whether a numeric member IID is published for riksdag_get_member.
`assignmentOffset`	No	Applied assignment offset.
`upstreamWarnings`	No	Warnings supplied by the source.
`serviceClassification`	No	Source-defined Swedish chamber service; unknown is retained.
`requestedAssignmentLimit`	No	Requested assignment limit before clamping and fitting.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and open-world behavior, so the description's added value is the domain caveat that assignment dates preserve source precision and do not establish historical sitting status. That is genuinely useful interpretation guidance beyond the annotations, though pagination/revision behavior is left to the schema.

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 short sentences with the core purpose front-loaded and the interpretive caveat second. Every sentence earns its place with no filler.

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?

An output schema exists and the annotations plus full parameter coverage carry most of the burden, so the description only needs purpose and caveats. It supplies both, though it could note that revision supports paging continuity to be fully self-contained.

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%, so all four parameters, including revision and assignment paging, are already documented in structured fields. The description adds no parameter-level detail beyond the schema, which is the expected baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read one member register entry and assignment history') and constrains the lookup to an exact member ID, which implicitly separates it from riksdag_search_members. It does not name the sibling explicitly, so a 4 rather than a 5.

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?

'By exact member ID' implies the caller must already have an ID, and the schema notes it comes from riksdag_search_members, so usage context is present but indirect. There is no explicit when-to-use/when-not statement or named alternative in the description itself.

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

All sweden-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.