Skip to main content
Glama

toll402 – EU & Nordic Data (x402)

dk_address

Validate and geocode a Danish address against the official Danish Address Register (DAR): normalised address, street, house number, floor/door, postcode, city, municipality code, DAR ids and coordinates (WGS84 + UTM32). Source: Klimadatastyrelsen, CC BY 4.0. Price 0.005 USD per call via x402.

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": {
      "q": "<q>"
    },
    "name": "dk_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesFree-text Danish address (street, number, optional floor/door, postcode/city)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / q / description
      Previous value: -"Free-text Danish address"New value: +"Free-text Danish address (street, number, optional floor/door, postcode/city)"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present, the description must disclose behavior, and it does: an authoritative source (Klimadatastyrelsen/DAR), a license (CC BY 4.0), a per-call cost (0.005 USD via x402), and the shape of the returned data, including WGS84 and UTM32 coordinates. It omits failure behavior for unmatched addresses (error vs. partial result) and whether the call is strictly read-only, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence led by the action, followed by compact provenance and pricing clauses. The long output-field enumeration is dense but earns its place because no output schema exists.

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?

With one simple parameter and no output schema, the description carries the return-value explanation itself (normalised address, DAR ids, coordinates) plus cost and source, which is what an agent needs. Missing only edge-case behavior for invalid or ambiguous addresses.

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?

There is only 1 parameter and its schema description coverage is 100%, so the schema already documents the free-text address format. The description adds no format syntax, examples, or constraints beyond what the schema states; baseline 3 applies.

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 states a specific verb pair (validate and geocode) against a named authoritative resource (the Danish Address Register/DAR), and enumerates the outputs. No sibling tool in the provided list does address work, so an agent can identify this tool from its name and description alone.

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?

Usage is implied by the phrase 'validate and geocode a Danish address,' but the description never states when to call this tool versus alternatives or what to do when it should not be called. Since none of the sibling tools are close substitutes, this implicit guidance is sufficient, but it is not explicit.

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.