Skip to main content
Glama
Sign In
Pleso Therapy MCP server

Pleso Therapy MCP server

by agus-pleso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get a Pleso therapist profile

get_therapist_profile
Read-onlyIdempotent

Retrieve a Pleso therapist's full public profile by ID from search results, including bio, credentials, specialties, languages, methods, client groups, intro video, and booking link.

Instructions

Full public profile of one Pleso therapist by id (from search_therapists): bio, education/diplomas, experience, languages, methods, client groups, all specialties by level, intro video and booking link.

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": {
      "therapist_id": "<therapist_id>"
    },
    "name": "get_therapist_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoPleso region = therapy language: en (English, worldwide), ua (Ukrainian), pl (Polish), ro (Romanian).en
therapist_idYesTherapist id from search_therapists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

While annotations already confirm it is readOnly and destructiveHint: false, the description adds the vital behavioral constraint that it fetches the 'Full public profile.' This signals to the agent that it will not access private or sensitive user data.

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 direct and avoids filler. The entire definition is focused on immediately stating what the tool returns, achieving maximum clarity with minimal wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that the schema covers all parameters and annotations cover safety, the description is highly complete. It clarifies exactly what the agent can expect in the data returned, which is the primary missing context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite the 100% schema description coverage, the description adds semantic value by listing the specific data included in the output (e.g., bio, education/diplomas, intro video, booking link). This helps the agent understand the nature and richness of the data it is requesting.

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 clearly defines the tool as retrieving the 'Full public profile of one Pleso therapist by id,' making it a specific action on a specific resource. It also helps differentiate it from 'search_therapists' by focusing on the single profile retrieval.

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 provides clear guidance by specifying that the therapist_id should be obtained 'from search_therapists,' establishing the required prerequisite for usage. The constraints are straightforward, requiring little complex decision-making.

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

Deploy Server

Other Tools