Masha Pelts DDS 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.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the 'does not publish/read private/send DMs' sentences largely restate the read-only profile. What the description genuinely adds is provenance ('verified public identities and sources'), i.e., that results are authoritative rather than scraped — useful but thin.

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 sentences, both earning their place: the first defines the operation and output, the second bounds the scope. Front-loaded with the core purpose and free of filler.

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 cover the safety profile, so return-value and side-effect details are not required. The single enum-constrained parameter also limits what needs explaining; only a note on what 'official/verified' means or how a missing profile is signalled would improve it.

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%, so the description must carry the parameter meaning; 'for this office' implies practice_id scopes the lookup to a single practice. That is minimal, though the enum constraint (single allowed value) makes further parameter elaboration largely unnecessary.

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+resource ('Identify the official website-linked Facebook and Instagram profiles for this office') and adds what is returned ('verified public identities and sources'). The resource is unmistakably distinct from every sibling (contact options, office hours, appointment link), so no schema opening is needed to disambiguate.

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 clauses ('does not publish posts, read private social accounts or send direct messages') clarify scope boundaries, which implicitly tells an agent this is a lookup-only tool. However, it never routes the agent among alternatives — e.g., that get_contact_options is the sibling for phone/email rather than social handles.

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?