Skip to main content
Glama
Sign In
Danish Law MCP Server

Danish Law MCP Server

by Ansvar-Systems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

format_citation

Formats Danish legal citations to standard conventions with full, short, or pinpoint options. Ensures citations follow Danish legal formatting rules.

Instructions

Format a Danish legal citation per standard conventions.

Formats:

  • full: "document 2018:218 3 kap. 5 §"

  • short: "2018:218 3:5"

  • pinpoint: "3 kap. 5 §"

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "citation": "<citation>"
    },
    "name": "format_citation"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format (default: "full")
citationYesCitation string to format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, so description carries full burden. It describes three output formats with examples, making behavior clear for a formatting tool. No destructive behavior expected.

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?

Extremely concise: one sentence of purpose plus a bullet list of formats. No wasted words, front-loaded with verb and resource.

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?

Given low complexity (2 params, no output schema), the description is sufficient. It explains purpose and formats. Could mention return value explicitly, but not necessary for such a simple tool.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by providing examples for each format option, clarifying what the 'format' parameter does beyond the enum values.

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 clearly states it formats a Danish legal citation per standard conventions. It distinguishes from sibling 'validate_citation' and other tools. The verb 'format' and resource 'citation' are specific.

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?

The description implies usage for formatting legal citations but does not explicitly state when to use or not use this tool versus alternatives like 'validate_citation'. No exclusions or conditions provided.

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

Deploy Server

Other Tools