Skip to main content
Glama
Sign In
Pleso Therapy MCP server

Pleso Therapy MCP server

by agus-pleso
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List concerns, methods and client groups

list_concerns
Read-onlyIdempotent

Lists the concerns, therapy methods, and client groups available in a region, with search codes you can pass to search_therapists to find matching therapists.

Instructions

The concerns (issues), therapy methods and client groups Pleso therapists in a region can be searched by, with codes usable in search_therapists.

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": "list_concerns"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoPleso region = therapy language: en (English, worldwide), ua (Ukrainian), pl (Polish), ro (Romanian).en
therapy_typeNoindividual therapy, or couple therapy (couple available in ua and pl).individual

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety behavior is fully covered without prose. The description adds one useful behavioral fact, that the returned codes are consumed by search_therapists, but it does not state the response shape (e.g. whether categories are returned as code/label maps) despite there being 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with no filler, and the downstream use of the codes is placed at the end where it reads as the payoff. The nested clause structure ('...client groups Pleso therapists in a region can be searched by') makes it marginally harder to parse than it needs to be.

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

Completeness3/5

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

For a two-parameter, fully documented read-only lookup this is close to sufficient, and the cross-reference to search_therapists covers the main integration question. Without an output schema, though, the description should hint at what comes back (three parallel lists of code/label pairs), which it leaves implicit.

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 coverage is 100% and both enum parameters carry detailed descriptions (region-to-language mapping, couple therapy availability in ua and pl). The description only echoes 'in a region' and adds no syntax or interaction detail, such as whether therapy_type narrows the returned methods, so baseline 3 applies.

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

Purpose4/5

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

The description names the three resources it enumerates (concerns/issues, therapy methods, client groups) and scopes them to a Pleso region, so the agent knows this is a taxonomy/lookup tool rather than a search. It is slightly obscured by an awkward passive construction ('...can be searched by'), which leaves the verb implicit, but the resource and its link to search_therapists are unambiguous.

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?

The phrase 'with codes usable in search_therapists' tells the agent exactly why to call this and what to do with the result, which is the key usage decision here. There is no explicit when-not guidance or statement about whether it must be called before searching, but the intended pipeline is clear from context.

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