Skip to main content
Glama

DentalUnlock

Check a current malpractice policy

check_my_current_policy
Read-onlyIdempotent

Returns the dentalunlock.com page where a dentist can upload their current malpractice policy's declarations page for review, and explains how the review works. Relevant when a dentist already has malpractice insurance and asks whether their premium is reasonable, mentions a renewal increase, or wants their current policy reviewed. Takes no inputs.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds meaningful context beyond them: the tool does not itself review the policy — it hands back a page and describes the review process, which sets correct expectations about the interaction being a handoff rather than a computation.

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, each earning its place: what it returns, when it is relevant, and that it needs no arguments. Front-loaded with the outcome, with the usage triggers immediately after.

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 parameters, no output schema, and rich annotations, the definition covers nearly everything an agent needs. The only soft spot is that 'returns the dentalunlock.com page' is slightly ambiguous about the return type (a URL string versus rendered content), which the absent output schema would otherwise have resolved.

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?

Zero parameters, so the baseline is 4, and the description explicitly confirms 'Takes no inputs,' removing any doubt an agent might have about needing to supply policy details. Nothing further is needed.

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?

Specific verb and resource: it 'returns the dentalunlock.com page' where a dentist uploads a declarations page, and 'explains how the review works.' The agent knows exactly what the tool yields (a page, not a review performed by the tool). It does not explicitly differentiate itself from estimate_dental_malpractice, so it stops short of a 5.

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?

Clear triggering conditions: dentist already has malpractice insurance and asks whether the premium is reasonable, mentions a renewal increase, or wants a current policy reviewed. That covers the 'when' well, but there are no exclusions ('when not to use') and no named alternative sibling for agents who land here but actually want an estimate or a new quote.

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