Pleso Therapy

Find a Pleso therapist

search_therapists

Read-onlyIdempotent

Search Pleso therapists and rank them by how strongly they work with the given concerns. Concerns can be short plain-language terms (e.g. "anxiety", "burnout", "grief", "panic attacks", "breakup") or codes from list_concerns. Returns up to 10 therapists with match score, matching specialties, methods, languages, a short bio and a profile/booking link on pleso.me.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_therapists"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`region`	No	Pleso region = therapy language: en (English, worldwide), ua (Ukrainian), pl (Polish), ro (Romanian).	en
`methods`	No	Preferred therapy methods, e.g. "CBT", "EMDR", "Gestalt", "psychoanalysis" (ranking bonus, not a filter).
`concerns`	No	Up to 5 short concern terms or codes. Do not pass personal narratives or identifying details.
`language`	No	Language the therapist must speak, e.g. "English", "Ukrainian", "Russian".
`therapy_type`	No	individual therapy, or couple therapy (couple available in ua and pl).	individual
`client_groups`	No	Relevant client groups, e.g. "LGBTQ+", "veterans", "expats", "students", "new parents" (ranking bonus).
`therapist_age`	No	Therapist age range preference.
`therapist_gender`	No	Only if the person states a preference.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds the return shape that annotations cannot: up to 10 therapists with match score, matching specialties, methods, languages, short bio and a pleso.me profile/booking link. It does not mention whether further results exist beyond the cap or how to page, which is the main residual gap given no output schema.

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, zero filler, front-loaded with capability then return value. The example list is compact and directly reduces invocation error.

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?

For a 9-optional-parameter discovery tool with high schema coverage, no output schema and rich annotations, the description covers purpose, ranking semantics and return contents adequately. The absence of pagination/truncation behavior and of explicit hand-off to get_therapist_profile keeps it just short of complete.

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?

Schema coverage is 89%, so the baseline is 3; the description still earns an increment by clarifying that concerns drive ranking strength and by supplying concrete plain-language examples ("anxiety", "burnout", "panic attacks") that the schema's generic wording does not. It correctly frames concerns as terms-or-codes, complementing list_concerns.

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?

Opens with a specific verb and resource ("Search Pleso therapists") plus the distinguishing mechanism: results are ranked by strength of match with the given concerns, not merely filtered. This separates it from siblings like get_therapist_profile (single therapist) and list_concerns (concern vocabulary) without the agent needing another schema.

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 use case is strongly implied and the description routes one sub-case (concern codes come from list_concerns), but there is no explicit when-to-use / when-not-to-use framing against get_therapist_profile or a direct booking flow. The agent must infer that this is the discovery step and get_therapist_profile the detail step.

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

All Pleso Therapy 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.