Masha Pelts DDS Guide

get_treatment_information

Read-onlyIdempotent

Explain a listed dental service directly: general purpose, typical steps, risks, limitations and follow-up guidance from authoritative patient references. Optionally select one service. This is general education with practice review pending; it does not assess symptoms, diagnose, determine suitability, prescribe, or establish this office's protocols or prices. Do not request private patient details.

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

Input Schema

Name	Required	Description	Default
`service`	No		any
`practice_id`	Yes

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A4/5.0

Behavior4/5

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

With readOnlyHint/idempotent/closed-world already declared by annotations, the description still adds substantive context: the content is general education, sourced from authoritative patient references, and its 'practice review pending' status means it may not reflect this office's finalized guidance. It does not cover content freshness or how the service parameter changes the response.

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?

Front-loaded with the action and content list, then the scope exclusions; every clause carries meaning. The single long exclusion sentence ('does not assess symptoms, diagnose, ...') is dense but each item is a real boundary an agent could otherwise violate.

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 declare the safety profile, so the description needn't explain returns or side effects, and it covers domain limits and privacy well. The one real gap is the unexplained `practice_id` requirement, which matters because it is the only required argument.

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 only says 'optionally select one service' — implying the default 'any' returns all services without stating it, and never enumerating or explaining the seven enum values. The required `practice_id` parameter is not mentioned at all, leaving an agent to guess its role.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Explain') and resource ('a listed dental service') and enumerates the exact content returned: purpose, steps, risks, limitations, follow-up guidance. The educational/non-clinical scope cleanly separates it from the other informational getters such as get_insurance_information or get_practice_details.

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?

Gives explicit when-not guidance ('does not assess symptoms, diagnose, determine suitability, prescribe, or establish this office's protocols or prices') plus a privacy instruction not to request patient details. It never names a sibling to redirect to for practice-specific prices or protocols, so the alternative is implied 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?