Skip to main content
Glama

DentalUnlock

Link to request dental malpractice quotes

start_malpractice_quote
Read-onlyIdempotent

Returns a dentalunlock.com link for starting a dental malpractice insurance quote request, with any known answers prefilled, and a summary of the next steps and typical timeline. Relevant when a dentist asks how to get actual malpractice quotes or wants to shop or switch their coverage. All inputs are optional. Does not submit anything; the dentist completes the request on dentalunlock.com.

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": "start_malpractice_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoUS state as a 2-letter postal code (e.g. TX, CA, DC). Full state names are also accepted.
specialtyNoThe dentist's specialty. Use "General Dentist" for general practice.
ada_memberNoIs the dentist an American Dental Association (ADA) member?
agd_memberNoIs the dentist an Academy of General Dentistry (AGD) member? Membership can affect the estimate.
policy_typeNooccurrence (default — no tail bill when leaving) or claims_made.
weekly_hoursNoAverage clinical hours per week: under_20, 20_32, or 33_plus (default 33_plus = full-time).
practice_typeNoWhere they practice: private_practice (default), dso (corporate/DSO), group_practice, or other.
sedation_levelNoHighest level of sedation the dentist provides. Default "None".
coverage_limitsNoPer-claim/annual-aggregate limits. Default 1M/3M (the most common).
graduation_yearNoYear the dentist graduated dental school (or will graduate this year). Provide this OR years_practicing.
years_practicingNoYears since dental school graduation. Used only if graduation_year is not given.
risk_management_ceNoHas the dentist completed risk-management CE in the last 12 months?
claims_last_5_yearsNoAny malpractice claim, lawsuit, or dental-board action in the last 5 years? Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context: it does not submit anything, the dentist completes the request on dentalunlock.com, and the return includes prefilled answers plus next steps and typical timeline. It does not discuss link expiry or whether prefilled data is transmitted, which keeps it from a 5.

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 sentences, front-loaded with what is returned, followed by the usage trigger and the no-side-effect caveat. No filler or repetition of the title.

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?

For a 13-parameter, zero-required link-generation tool with no output schema, the description covers what is returned (link, prefilled answers, next-steps summary), that nothing is submitted, and when to use it. An agent has everything needed to call it correctly.

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% with 13 well-documented optional parameters, so the schema carries the semantic load. The description adds only the useful framing that 'All inputs are optional' and that known answers are prefilled, without explaining defaults or interactions beyond what the schema already states.

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?

The description names a specific verb and resource — it returns a dentalunlock.com link for starting a malpractice quote request — and states the scope (prefilled answers plus a summary of next steps and timeline). It also implicitly separates itself from the estimation sibling by framing the tool around 'actual malpractice quotes' and shopping/switching coverage.

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?

It gives a clear trigger condition: 'Relevant when a dentist asks how to get actual malpractice quotes or wants to shop or switch their coverage.' It does not explicitly name a when-not case or point to estimate_dental_malpractice as the alternative for price estimates, so it stops short of full routing guidance.

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.

Resources