Skip to main content
Glama
Sign In
Open Dental MCP

Open Dental MCP

by MaxilloCA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_appointment

Read-onlyIdempotent

Retrieve a single appointment by its exact internal AptNum to view its details. Use it when you know the appointment ID and need that specific record.

Instructions

Fetch one appointment by its exact internal AptNum.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "aptnum": "<aptnum>"
    },
    "name": "get_appointment"
  }
}

Input Schema

NameRequiredDescriptionDefault
aptnumYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds only the requirement that the key be an exact internal AptNum (no fuzzy matching), and says nothing about not-found behavior or error handling.

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?

A single well-formed sentence with the lookup key qualification front-loaded and no filler; every word contributes.

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?

For a one-parameter read tool with an output schema, the definition is close to sufficient — return values need no explanation. The remaining gap is what happens when the AptNum does not resolve, which the annotations do not cover and the description omits.

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 0%, so the schema carries no per-parameter meaning beyond type integer and minimum 1. The description compensates partially by establishing that the value is an internal AptNum requiring an exact match, but gives no format, example, or hint about where to obtain one.

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 and resource ('Fetch one appointment') plus a key qualifier ('by its exact internal AptNum') that separates it from the search-style sibling find_appointments. It does not name the sibling explicitly, but the singular/exact-match framing is unambiguous.

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 rather than stated: an agent can infer it should call this when it already holds an AptNum, and should search otherwise. There is no explicit when-to-use/when-not statement or named alternative, leaving the routing inference to the reader.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools