Skip to main content
Glama
Sign In

Pleso Therapy

by io.github.agus-pleso
OverviewDiscussionsAdmin

Crisis and emergency contacts

get_crisis_resources
Read-onlyIdempotent

Emergency numbers and free crisis/suicide-prevention lines for a country (UA, PL, RO, GB, IE, US, CA, DE; others get the international directory). For situations where someone may be in danger or thinking about suicide or self-harm.

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

Input Schema

NameRequiredDescriptionDefault
countryNoISO country code or country name, e.g. "PL", "Ukraine". Omit if unknown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context. It does: it discloses the coverage set and, importantly, the fallback behavior for unsupported countries (international directory) — behavior an agent could not infer from the 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. The resource and its country coverage come first, followed by the qualifying use case, so an agent reading only the opening clause can already route correctly.

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 single optional-parameter read tool with full schema coverage and no output schema, this is nearly complete: coverage, fallback, and use condition are all present. Only the shape of the return (what fields a crisis line entry has) is unspecified, which is a minor gap for a safety-critical tool.

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 100% and the parameter already documents ISO code or country name plus 'omit if unknown', so a 3 baseline applies. The description adds meaning beyond the schema by enumerating which countries yield localized data and what happens otherwise, which tells the agent the parameter is optional and safe to skip.

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 states a specific resource type (emergency numbers and free crisis/suicide-prevention lines) plus scope (per-country, with a defined supported set and a fallback to an international directory). The resource is obviously distinct from the therapist-related siblings, though no sibling is named explicitly.

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 gives a clear triggering condition: 'situations where someone may be in danger or thinking about suicide or self-harm.' That is strong positive guidance, but there is no explicit when-not or routing to an alternative tool (e.g. for non-crisis emotional support).

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

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