Skip to main content
Glama
Sign In
Open Dental MCP

Open Dental MCP

by MaxilloCA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

find_procedurelogs

Read-onlyIdempotent

Retrieves procedure records for a patient, including planned and completed work, with optional date-range filtering to review treatment history.

Instructions

Read a patient's procedure records; these may include planned and completed work.

Optional inclusive YYYY-MM-DD ProcDate bounds filter locally. Follow next_offset even when results is empty. Do not interpret every procedure as completed treatment.

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": {
      "patnum": "<patnum>"
    },
    "name": "find_procedurelogs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
patnumYes
date_endNo
date_startNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, the description discloses two non-obvious behaviors: date bounds are applied client-side ('filter locally') and the caller must keep following next_offset even when results is empty. It also warns that records may be merely planned, which prevents a costly misreading of results.

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?

Three short, front-loaded sentences with no filler; the most important caveats are easy to find. A slightly tighter grouping of the two filtering/pagination notes would make it ideal.

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?

Given annotations covering safety and an existing output schema, the description covers the domain-specific traps (planned vs completed, local date filtering, empty-result pagination). Only the limit parameter and the meaning of the patient number are left to the schema.

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 0%, so the description must carry parameter meaning. It clarifies date_start/date_end as inclusive YYYY-MM-DD bounds and ties offset to a next_offset token, but limit, offset ranges, and patnum semantics remain undocumented outside the bare schema types.

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: 'Read a patient's procedure records.' The mention of planned vs completed work scopes the content type, which implicitly separates it from appointment or comm-log siblings, but no sibling is named explicitly.

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 guidance is implied through the caveat 'Do not interpret every procedure as completed treatment' and the pagination instruction, but it never says when to prefer this over other lookups or what prerequisites (e.g. a valid patnum) are needed.

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