Masha Pelts DDS 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 28, 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 readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real context: it discloses that unverified channels are explicitly marked, a data-quality trait not captured in annotations. It also reaffirms the no-side-effects boundary in domain terms.

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 tight sentences with the positive capability front-loaded and the boundary statement second. Every clause carries information; nothing is redundant with the annotations.

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, so return values need no explanation, and the single enum parameter is low-risk. The definition covers capability and side-effect boundaries adequately, with only the sibling-routing guidance missing.

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, but the name is self-explanatory and the enum constrains it to a single known value. The description adds no meaning about what practice_id identifies or how it relates to find_practices, so it neither compensates for the gap nor creates confusion.

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 (Get) plus concrete resources: office-specific phone, email, verified SMS options, and feedback/contact instructions. It is clearly distinguishable from siblings like get_practice_details or get_social_profiles, though 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?

The negative scope ("does not collect patient details, send messages, publish feedback or place a call") usefully rules out misuse, but it never says when to pick this over get_practice_details or get_social_profiles, which overlap on contact information. Usage is implied by the resource list rather than stated.

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

All Masha Pelts DDS 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?