Renaissance Dental Guide

get_contact_options

Read-onlyIdempotent

Get office-specific phone, email, verified SMS options, and feedback/contact instructions. Clearly marks unverified channels. This information tool does not collect patient details, send messages, publish feedback or place a call.

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_contact_options"
  }
}

Input Schema

Name	Required	Description	Default
`practice_id`	Yes

Output Schema

Name	Required	Description	Default
`practice_id`	Yes
`practice_name`	Yes
`source_status`	Yes
`contact_options`	Yes
`sources_checked`	Yes
`information_may_be_outdated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026

addedOutput schema / properties / contact_options / properties / callback_instruction
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / contact_options / required

Previous value: -[
-  "channels",
-  "delivery_supported",
-  "feedback_collection_supported",
-  "feedback_instruction",
-  "clinical_contact_instruction"
-]New value: +[
+  "channels",
+  "delivery_supported",
+  "feedback_collection_supported",
+  "feedback_instruction",
+  "clinical_contact_instruction",
+  "callback_instruction"
+]

AddedOct 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower; the description adds useful behavior context by noting that unverified channels are clearly marked and that no side effects such as messaging or calls occur. It still omits details like permissions or rate limits, but the added disclosure is meaningful.

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?

The description is short, front-loaded with the resource list, and every sentence adds useful scope or boundary information. There is no redundant or wasted wording.

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 simple read-only lookup tool, the description covers purpose, output marking, and non-actions, while the output schema and annotations cover return values and safety. The only notable omission is explanation of the required practice_id parameter.

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?

The description says "office-specific" but never mentions the required practice_id parameter or its enum value, and schema description coverage is 0%. The single-value enum limits ambiguity, but the description does not add the parameter meaning it should under low coverage.

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?

The description uses a specific verb ("Get") and enumerates the resources (phone, email, verified SMS options, feedback/contact instructions), making the tool's scope clear. It does not explicitly distinguish itself from siblings such as get_social_profiles or get_office_hours, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for use as an information-retrieval tool and explicitly excludes actions like collecting patient details, sending messages, publishing feedback, or placing calls. However, it does not name alternative tools or state when to choose this over siblings, so it is not a full 5.

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?