Renaissance Dental Guide

get_social_profiles

Read-onlyIdempotent

Identify the official website-linked Facebook and Instagram profiles for this office. Returns verified public identities and sources directly; does not publish posts, read private social accounts or send direct messages.

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

Input Schema

Name	Required	Description	Default
`practice_id`	Yes

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world, so the bar is lower. The description still adds real value by specifying that results are verified public identities with their sources, and by excluding post publishing, private-account reads, and DMs — clarifying both data provenance and the tool's operational boundary.

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: what is returned first, then the exclusion boundary. Slight redundancy in enumerating three separate things the tool does not do, but each clause disambiguates a plausible misread, so the cost is minor.

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?

With an output schema covering return values, four read-only annotations, and a single constrained enum parameter, the description needs only purpose and boundary — both are present. Missing only edge-case behavior such as what is returned when no verified profiles exist.

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?

Schema description coverage is 0%, and the description never explains practice_id directly, only referring loosely to 'this office'. The single-value enum ('renaissance-dental') makes the parameter effectively self-documenting, so the schema-side gap is small, but the description adds no explicit meaning.

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?

The description names a specific verb ('Identify') and a specific resource ('official website-linked Facebook and Instagram profiles'), and scopes it with qualifiers ('official', 'website-linked', 'verified public identities'). No sibling tool returns social profiles, so the resource alone distinguishes it cleanly from get_office_hours, get_contact_options, and the rest.

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 implied by the resource ('for this office') but the description never states when an agent should call this versus another sibling, nor any preconditions. The negative clauses rule out unrelated actions rather than guiding tool selection, so this stays at minimum-viable.

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?