Skip to main content
Glama
Open Dental MCP
by MaxilloCA

health_check

Read-onlyIdempotent

Verifies API connectivity through one provider and confirms the Open Dental REST API is reachable before other read-only lookups. It does not check other permissions.

Instructions

Check API connectivity using one provider; this does not verify other permissions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety behavior needs no restating. What the description adds is genuinely non-obvious: a successful check is scoped to a single provider and is not evidence that other permissions work, which prevents a false-positive conclusion. It could go further by saying whether a failure is retryable or returned as an error.

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 sentence with the capability front-loaded and the limitation immediately after it; no filler, no restatement of the name. Every clause changes how the agent interprets the result.

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 no-parameter health check with an output schema (so return values need no explanation), the description covers the essential risk — over-trusting a positive result. Minor gap: no guidance on failure handling or retry behavior, though annotations already confirm it is safe and idempotent to repeat.

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?

The tool takes zero parameters, so there is no schema semantics for the description to compensate for; baseline 4 applies. The mention of "one provider" is a fixed runtime choice rather than an input, and it correctly implies no arguments are 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?

States a specific verb and resource ("Check API connectivity") and scopes it ("using one provider"), which is plainly distinct from the data-lookup siblings. It stops short of naming an alternative, but no alternative performs the same job, so the purpose 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 only implied: an agent can infer this is a diagnostic/preflight call, but the description never says when to run it (startup vs. after an error) or what to do with a failure. The one explicit exclusion — it does not verify other permissions — is a scope caveat rather than a use case.

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