Skip to main content
Glama
Sign In
Open Dental MCP

Open Dental MCP

by MaxilloCA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_clinics

Read-onlyIdempotent

Read one page of clinic records from Open Dental, using limit and offset to control pagination and next_offset to continue.

Instructions

Read one page of clinics. Follow next_offset for further pages.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description's contribution is the paging behavior, but it omits ordering guarantees, whether a total count is returned, and any rate-limit or scope constraints — gaps that matter for a paginated listing.

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?

Two short sentences, front-loaded with the core action and then the paging hint. Nothing is padded or redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values needn't be explained, and the tool has only two optional parameters. Still, the description leaves the limit/offset contract and the mismatch between "next_offset" and the offset parameter unaddressed, which is more gap than a listing tool of this simplicity should carry.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning, but it never mentions limit or offset semantics. Worse, it references "next_offset", a name that does not exist in the input schema (which defines offset), leaving the agent to infer that this is an output field to echo back.

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?

Names a concrete verb and resource ("Read one page of clinics") and adds the pagination scope, so the agent immediately knows this is a paged list read of clinics. It does not explicitly distinguish itself from the sibling list_ tools, but the resource noun 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?

The second sentence gives real operational guidance for iteration ("Follow next_offset for further pages"), which is more than a bare description. However there is no statement of when to prefer this over alternatives or any preconditions, so usage is only implied.

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