Skip to main content
Glama

Find dental clinics for emergency care in Norway

tannlege_akutt
Read-onlyIdempotent

Find an emergency dentist (akutt tannlege) in Norway: dental clinics that say they take emergency patients, optionally in one county (fylke). Each clinic's akutt is "vakt" only when its emergency duty has a stored quote from the source (badge «Akuttvakt»), and "accepts" when the clinic says it takes emergency patients («Tar imot akuttpasienter»). count is the number of matching clinics. Each clinic has its address, phone and profile URL, and when known its opening hours and online booking link. The response also has advice on the municipal out-of-hours dental service (kommunal tannlegevakt).

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

Input Schema

NameRequiredDescriptionDefault
fylkeNoLimit to clinics in this county. Examples: 'Oslo', 'Vestland'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnlyHint/idempotentHint annotations, the description explains the meaning of each returned value: `akutt` is "vakt" only when a stored source quote supports the badge, and "accepts" when the clinic self-declares. It also lists per-clinic fields and the presence of out-of-hours (kommunal tannlegevakt) advice, so an agent knows exactly what evidence backs each record.

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 core purpose is front-loaded in the first sentence, and the remaining sentences are dense with substantive detail about value semantics. It is somewhat long and mixes output-contract information into the summary, but no sentence is filler.

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, so the description carries the full burden of explaining returns, and it does: `count`, per-clinic address/phone/profile URL, known opening hours and booking link, plus the advice field. An agent can anticipate the response shape without extra documentation.

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 schema already provides examples for `fylke`. The description adds that the filter is optional and limited to a single county, which is a small increment over the structured field. This is the expected baseline when the schema does 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?

The description gives a concrete verb and a tightly scoped resource: find dental clinics that accept emergency patients in Norway, with an optional county filter. It is specific enough to be distinguishable from a general clinic search. It does not name any sibling tool (tannlege_search, tannlege_kjeder, etc.) to make that differentiation explicit.

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?

The emergency-care framing implies when the tool applies, but there is no explicit statement about when to use a sibling instead, for example, general searches use tannlege_search or chain lookups use tannlege_kjeder. When-not conditions and prerequisites are left to inference.

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.