Skip to main content
Glama

Get therapist profile

get_therapist
Read-only

Full public profile of one verified therapist by profile slug (the last path segment of a profile_url), including bio, credentials, and for registered professions the publicly displayed registration numbers checkable against the NMC/RCI registers.

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": {
      "slug": "<slug>"
    },
    "name": "get_therapist"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesProfile slug, e.g. 'shaswatee-behera'

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?

The description is consistent with readOnlyHint=true and adds real context beyond the annotation: only verified therapists' public data is returned, and registration numbers are those displayed publicly and checkable against the NMC/RCI registers. It does not cover error behavior for an unknown or unverified slug, so it stops short of the top score.

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 front-loaded sentence that leads with what is returned before the keying detail, with no filler. It is dense with clauses (bio, credentials, registration registers) but every clause carries information an agent would otherwise have to guess.

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?

With one fully documented parameter, a read-only annotation, and no output schema, the description carries the right burden by enumerating the fields returned (bio, credentials, registration numbers). Missing only edge-case behavior for invalid or unverified slugs.

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 already gives an example slug, so the baseline is met; the description adds genuine meaning by defining the slug as the last path segment of a profile_url, which tells the agent where to source the value. The parameter is singular and unambiguous, so no more is needed.

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 and resource: retrieves the full public profile of a single verified therapist, keyed by profile slug. The inclusion list (bio, credentials, registration numbers) and the 'one ... by slug' framing make it clearly distinct from the sibling search_therapists and list_filter_options tools.

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?

Usage is only implied: the parenthetical explaining that the slug is the last path segment of a profile_url tells the agent what input to supply, and 'one ... by profile slug' hints it is for direct lookup rather than discovery. There is no explicit 'use this when you already have a slug, otherwise use search_therapists' routing statement or any exclusion.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources