Danmark Data

Who owns this Danish phone number

phone_lookup

Read-onlyIdempotent

Identify a Danish phone number: operator, mobile/landline/service, region, companies that registered it in CVR, and a spam/trust verdict from user reports.

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": {
      "number": "<number>"
    },
    "name": "phone_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`number`	Yes	Danish number, 8 digits; spaces and +45 are fine

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds genuine context about data sources — CVR registry registrations and user reports — which explains where the trust verdict comes from. It says nothing about coverage gaps (e.g. unregistered or non-Danish numbers) or how fresh the user-report signal is.

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?

One compact sentence that front-loads the verb and resource, then lists returnable facets with no filler. The colon-list style is dense but readable and wastes no words.

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?

An output schema exists, so return structure need not be explained, and with one fully documented parameter this is close to complete for a read-only lookup. The remaining gap is selection guidance against the spam-specific sibling, which the definition never 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?

Schema coverage is 100% and the single parameter already documents the 8-digit Danish format and tolerance for spaces and +45, so the description adds no parameter meaning. Baseline 3 applies when the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Identify") and resource ("a Danish phone number") and enumerates the returned facets: operator, line type, region, CVR registrants, and a spam/trust verdict. That is clearly distinguishable from vehicle/address/company siblings, but the definition does not distinguish itself from phone_spam_check, which the shared spam verdict facet suggests overlaps.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given, and no alternative is named. The overlap with phone_spam_check is left unresolved, so an agent must guess whether this general lookup supersedes the dedicated spam tool or duplicates it.

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

All Danmark Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?