Skip to main content
Glama

Get full details for a dental clinic

tannlege_info
Read-onlyIdempotent

Get the full record of one dental clinic in Norway, a dentist (tannlege) or specialist practice, by organisation number (org_nr) or id. Returns name, address, phone, mobile, e-mail, website, online booking link, Helfo status, the emergency claim («Akuttvakt» only when an emergency duty has a stored quote from the source; «Tar imot akuttpasienter» when the clinic says it takes emergency patients), specialties, chain, specialists, treatments, opening hours, payment options, the clinic's own description and profile URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tannlege_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoClinic UUID (alternative to org_nr)
org_nrNo9-digit Norwegian organisation number. Example: '912345678'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is clear. The description adds useful behavioral context by detailing the returned fields and clarifying conditional emergency-claim semantics such as «Akuttvakt» versus «Tar imot akuttpasienter».

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 front-loaded with the core purpose and then lists return fields in a dense but useful single sentence. There is little waste, though the long field list makes it less scannable than shorter definitions.

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?

Because there is no output schema, the description carries the burden of explaining what is returned, and it does so thoroughly. It is only slightly incomplete in not stating what happens if neither id nor org_nr is supplied, or which identifier wins if both are present.

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 description coverage is 100%, so both id and org_nr are already fully documented in the schema. The description restates that lookup can be done by organisation number or id but adds no format, precedence, or conflict-handling details beyond the schema.

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?

The description states a specific verb and resource: get the full record of one dental clinic by org_nr or id. It implicitly distinguishes itself from sibling tools like tannlege_search by emphasizing a single full record, but it does not explicitly name those alternatives.

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 need to supply an org_nr or id and by the phrase 'one dental clinic,' which suggests this is a detail lookup rather than a search. However, there is no explicit guidance on when to use this instead of tannlege_search, tannlege_akutt, or other siblings.

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.