Skip to main content
Glama
aneal99

datafordeler-dar

by aneal99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search streets and addresses by text prefix (API key)

dar_search_addresses
Read-onlyIdempotent

Find Danish streets, access addresses, and unit addresses by exact text prefix via Datafordeler GraphQL; returns matching IDs and text.

Instructions

Find streets, access addresses or unit addresses whose official text starts with a prefix, via the Datafordeler GraphQL service. REQUIRES DATAFORDELER_API_KEY.

The service supports prefix matching only (startsWith): no fuzzy, substring or typo-tolerant search, and it is CASE-SENSITIVE. Write the prefix the way DAR writes it: "Vejnavn husnummer, postnr By". This tool upper-cases the first letter for you; the rest must match exactly, including Danish letters (æ, ø, å).

level:

  • "street": match street names (NavngivenVej), e.g. "Rentemester" -> Rentemestervej in København (0101) and Hvidovre. Returns street id, name and administering municipality code. Feed the id to dar_list_access_addresses({ street_id }) to enumerate house numbers.

  • "access_address" (default): match entrances, e.g. "Rentemestervej 8" -> Rentemestervej 8, 80, 82, ... Results are NOT ranked; an exact house number is one of several prefix matches, so add ", 2400" or pick by house_number.

  • "address": match unit addresses including floor/door, e.g. "Oehlenschlægersgade 35, st".

Returns ids and text only. Follow up with dar_get_access_address / dar_get_address for coordinates, municipality and postcode. Paginate with the returned next_cursor.

Example: dar_search_addresses({ query: "Rentemestervej 8, 2400", limit: 5 }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoCursor from a previous result's next_cursor, for the next page.
levelNoaccess_address
limitNo
queryYesText prefix, e.g. "Rentemestervej 8" or, for level "street", "Rentemester".
only_currentNoKeep only status 3 (gældende) records.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/openWorld/destructive=false, but the description adds substantial non-obvious behavior: the API key requirement, case-sensitivity, automatic first-letter upper-casing, exact-match requirement for Danish letters, unranked results, and cursor pagination. This is well beyond what the structured fields convey.

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 critical operational facts (prefix-only, case-sensitive, API key) are front-loaded, and the level breakdown is well structured with examples. It is somewhat long, with a few redundant asides (e.g. the worked example plus inline examples), but nearly every sentence carries load.

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?

There is no output schema, and the description explicitly says the return is ids and text only, tells the agent which sibling to call for coordinates/postcode, and covers pagination. Nothing needed to call this correctly 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?

With 60% schema coverage, the description compensates well: it explains the query prefix format ('Vejnavn husnummer, postnr By'), the meaning of each level enum value, and the after cursor for pagination. It does not cover limit behavior or only_current beyond what the schema already states (status 3 gældende), so it stops short of a 5.

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?

States a specific verb (find) and resource (streets, access addresses, unit addresses) plus the matching semantics (official text starts with a prefix). It clearly distinguishes itself from sibling getters by framing itself as the prefix-search entry point and naming the follow-up tools (dar_list_access_addresses, dar_get_access_address).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly enumerates the three level modes with when-to-use guidance and examples for each, states the default, and names the alternative tools to call afterward. It also states the negative constraint (no fuzzy, substring or typo-tolerant search) and how to disambiguate unranked results.

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