Skip to main content
Glama
nordic-registry-mcp-server

nordic-registry-mcp-server

by olgasafonova

denmark_search_by_phone

Read-only

Find a Danish company by phone number when you lack a company name or CVR. Returns company name, CVR number, and address if matched; empty result otherwise.

Instructions

Find Danish company by phone number. USE WHEN: you only have a phone number, not a company name or CVR. Returns company name, CVR number, and address if found; empty result if no match. +45 prefix auto-removed. Not all companies have registered phones.

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": {
      "phone": "<phone>"
    },
    "name": "denmark_search_by_phone"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYesDanish phone number registered to the company, 8-15 digits; a +45 country prefix and separators are stripped automatically, e.g. 33121212

Output Schema

NameRequiredDescriptionDefault
foundYes
companyNo
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • changedInput schema / properties / phone / description
      Previous value: -"required"New value: +"Danish phone number registered to the company, 8-15 digits; a +45 country prefix and separators are stripped automatically, e.g. 33121212"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuinely new behavior: the exact return fields, that a miss yields an empty result rather than an error, prefix stripping, and the caveat that not all companies have registered phones. The idempotentHint=false flag on a pure lookup is left unexplained, which is the one gap.

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?

Three short sentences, front-loaded with purpose then usage condition, then return shape. No filler or repetition; each clause carries distinct information.

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?

For a one-parameter lookup with an output schema, the definition covers purpose, usage condition, result shape, no-match behavior, and data-quality caveat, which is nearly everything needed. Minor omission: no mention of rate limits or of how this differs from the sibling phone-based tool.

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?

With a single parameter at 100% schema coverage, the schema already documents digit range and automatic separator/prefix stripping, and the description only restates the +45 behavior. The description adds no constraint beyond the schema, so 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?

States a specific verb and resource ("Find Danish company by phone number") and immediately scopes it against the other lookup modes ("not a company name or CVR"), so an agent can distinguish it from name- or CVR-based siblings without opening the schema.

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?

The "USE WHEN: you only have a phone number" clause gives explicit positive guidance plus an implicit exclusion of name/CVR searches. It stops short of naming a concrete alternative tool (e.g. the similarly-named denmark_get_by_pnumber), leaving the agent to infer the choice between the two phone-capable entries.

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