Renaissance Dental Guide

get_capabilities

Read-onlyIdempotent

Check what this practice connection can do, including direct information access and whether scheduling or insurance eligibility APIs are connected. Distinguishes available facts from unsupported live actions.

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": {
      "practice_id": "<practice_id>"
    },
    "name": "get_capabilities"
  }
}

Input Schema

Name	Required	Description	Default
`practice_id`	Yes

Output Schema

Name	Required	Description	Default
`practice_id`	Yes
`capabilities`	Yes
`practice_name`	Yes
`source_status`	Yes
`sources_checked`	Yes
`information_may_be_outdated`	Yes
`browser_required_for_information`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A3.7/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 closed-world, so the safety profile is covered. The description adds genuinely new behavioral context by saying the response separates real capabilities from unsupported live actions, which shapes how much the agent should trust downstream calls.

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?

Two front-loaded sentences that state the resource and the key differentiator with no filler. Slightly dense wording ('including direct information access') but nothing wasted.

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?

An output schema exists and annotations are rich, so return values and safety need no explanation; the description supplies the decision-relevant framing. A single constrained parameter keeps the surface small, leaving only minor room for improvement.

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?

Only one parameter (practice_id) with 0% schema description coverage; the description adds nothing about it. However, the parameter is constrained by a single-value enum (renaissance-dental), which makes its meaning self-evident, so the gap is small.

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+resource: check what a practice connection can do, including which live APIs (scheduling, insurance eligibility) are wired up. It is distinguishable from the get_* data siblings because it reports capability/availability rather than returning a data payload, though it never names a sibling 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?

The phrase 'Distinguishes available facts from unsupported live actions' hints that this should be consulted before assuming another tool will work, but it never states when to call it, when not to, or which alternatives it replaces. Usage must be inferred from the sibling set.

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

All Renaissance Dental Guide tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?