Hämta regeringsdokument (alla typer: pressmeddelanden, propositioner, SOU, etc.)
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Dokumenttyp (om känd). Om inte angiven, söks i alla typer. | |
| document_id | Yes | ID eller URL-del för dokumentet |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden, but it does not disclose any behavioral traits beyond listing document types. It does not state return format, content vs. metadata, error behavior, or required permissions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence that efficiently states the tool's purpose and scope. It is front-loaded and contains no redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has no output schema and no annotations, yet the description does not explain return values, content type, or any side effects. For an agent choosing among several document-related siblings, this is incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already provides full descriptions for both parameters (document_id and type) with 100% coverage. The description adds little beyond reiterating the type list, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves government documents of all types, using a specific verb ('Hämta') and resource ('regeringsdokument'). It lists example types but does not explicitly differentiate from sibling tools like get_dokument.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives such as get_dokument or get_propositioner. It only describes the function, leaving the agent to infer appropriate usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.