Skip to main content
Glama

Search Norwegian dental clinics

tannlege_search
Read-onlyIdempotent

Find a dentist (tannlege), orthodontist (kjeveortoped) or emergency dentist (akutt tannlege) in Norway by place, county (fylke), specialty, Helfo direct billing or emergency care. The request can go in query as written, such as 'kjeveortoped i Bergen med Helfo-avtale'; the response's tolkning shows how it was read, and count is the number of matching clinics. Each clinic has its name, address, postcode, place, county, phone, website, Helfo status, emergency status (akutt) and profile URL, and when known its online booking link, opening hours, specialties, chain and a price level that has a source.

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_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
akuttNoIf true, only return clinics with an emergency claim: «Akuttvakt» backed by a stored source quote, or «Tar imot akuttpasienter».
fylkeNoNorwegian county (fylke). Examples: 'Oslo', 'Vestland', 'Rogaland'
helfoNoIf true, only return clinics with Helfo direct-billing agreement
limitNoMax results (default 10, max 25)
queryNoFree-text search (name or city). Examples: 'Oslo tannklinikk', 'kjeveortoped Bergen'
spesialitetNoSpecialty slug. Examples: 'kjeveortopedi', 'endodonti', 'periodonti'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / akutt / description
      Previous value: -"If true, only return clinics with emergency-duty (akuttvakt)"New value: +"If true, only return clinics with an emergency claim: «Akuttvakt» backed by a stored source quote, or «Tar imot akuttpasienter»."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the lower bar applies; the description still adds real value by explaining that `tolkning` shows the interpreted query and `count` the match total, plus what each clinic record contains. It stops short of stating result ordering or empty-result behavior.

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?

Two sentences, front-loaded with the verb and domain, then the query convention, then the return shape. The second sentence packs a long field list, but every clause carries information an agent would otherwise have to guess.

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 no output schema, the description does the work of describing the return payload (name, address, Helfo status, akutt, booking link, price level with source), which is substantial. Minor gaps remain around ranking and behavior when zero clinics match.

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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by showing that multiple filters can be expressed in one free-text `query` and that the parse is echoed in `tolkning`, which is meaning beyond the schema's per-field docs.

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 ('Find') and resource (dentist/orthodontist/emergency dentist in Norway), plus the filter axes (place, fylke, specialty, Helfo, emergency). It does not explicitly distinguish itself from tannlege_akutt or tannlege_stats, so an agent must infer the boundary from names alone.

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?

Makes clear how to call it: a natural-language request can be passed in `query` verbatim, with a concrete example ('kjeveortoped i Bergen med Helfo-avtale'). It offers no explicit when-not or named alternative tool, which keeps it below a 5.

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.