get_ledamot
Hämta detaljer om en ledamot
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| intressent_id | Yes | Ledamotens intressent ID |
Riksdag & Regering MCP
TDQS
C2.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'Hämta detaljer' and does not specify whether this is a read-only operation, what the return format is, or how errors are handled.
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 a single short sentence with no redundant words, making it highly concise and front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of annotations and an output schema, the description is too terse. It does not explain what 'detaljer' include, how to obtain the intressent_id, or what the response might look like. A simple get-by-id tool still benefits from additional context about its expected behavior.
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?
The input schema fully describes the intressent_id parameter with 100% coverage, and the description adds no additional meaning beyond the schema. This meets the baseline of 3 for high schema coverage.
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?
The description 'Hämta detaljer om en ledamot' clearly states the action (get) and resource (member), with 'detaljer' specifying the scope. It distinguishes itself from sibling tools like search_ledamoter by implying a direct ID-based lookup rather than a search, but it does not explicitly name alternatives.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as search_ledamoter. The description does not mention prerequisites, context, or exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.3/5.0
Disambiguation3/5
Many tools target specific data types (documents, speeches, votes, members), but there is notable overlap between similar fetch/search tools, such as get_dokument vs get_dokument_innehall, and search_dokument vs search_dokument_fulltext. Descriptions help, but an agent could easily select the wrong tool for a task.
Naming Consistency2/5
Tool names mix Swedish and English inconsistently (e.g., get_betankanden vs get_dokument, get_regering_document vs get_g0v_document_content). Prefixes vary (get, search, fetch, list, batch, enhanced, analyze, summarize) without a clear pattern, making the set feel haphazard.
Tool Count2/5
With 32 tools, the server is heavy and likely overwhelms an agent. While the domain is broad, many tools could be consolidated (e.g., paginated fetch variants, multiple search methods), and the count exceeds the typical well-scoped range.
Completeness4/5
The server covers a wide range of Swedish government data: documents, members, votes, questions, reports, and calendars. Minor gaps exist, such as no direct single-vote retrieval or per-member document listing, but the core informational needs are well covered.