se-eli-mcp

se_coverage

Read-onlyIdempotent

Check which Swedish statutes this connector covers, how they are sourced, and known gaps. Call before concluding a search is empty to distinguish missing law from connector limitations and get fallback sources.

Instructions

Declare what this connector covers, how it is sourced, and what it does NOT cover.

Call this before telling a user that the law "does not contain" something, and whenever a search comes back empty: the absence may be a gap in this connector rather than in the law. Every gap carries a fallback saying where to look instead.

Returns: Coverage with families, an as-of note, and a non-empty list of known gaps.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	No		ok
`families`	No
`as_of_note`	Yes	States what the dates mean, and what they do not promise.
`known_gaps`	No	Never empty. An empty list would mean 'not checked', not 'no gaps'.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.3.3Aug 28, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already mark it read-only/open-world/idempotent; the description adds crucial context: an empty result may reflect a connector gap, not the law, and every gap includes a fallback location. This materially shapes agent behavior and supplements the structured hints without contradicting them.

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 front-loaded with the core purpose, then gives actionable usage guidance, fallback behavior, and return shape. Every sentence earns its place and there is no 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?

For a no-parameter, no-side-effect tool with an output schema, the description fully covers when to call it, what behavioral caveat matters (open world), and what the response contains. Nothing necessary for correct invocation is 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?

The tool has zero parameters, so schema coverage is trivially complete. The description does not need to document parameter meaning; baseline 4 applies because no parameter semantics are absent.

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 names a specific verb and resource: 'Declare what this connector covers, how it is sourced, and what it does NOT cover.' It distinguishes this meta/coverage tool from the sibling search/get tools by framing it around connector gaps rather than law content.

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?

It gives explicit trigger conditions: call before claiming the law does not contain something and whenever a search returns empty. It does not explicitly name sibling alternatives, but the fallback pointer and open-world framing make the intended use clear.

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

Deploy Server