ChooseHelp Treatment Directory

Get expert profile

get_expert

Read-only

Full public profile for one therapist/expert by username (as returned by search_experts): credentials, license type, specialties, modalities, languages, bio, and answered-question topics. Contact details live on the linked profile page.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`username`	Yes	Expert username from search_experts

Output Schema

TableJSON Schema

Name	Required	Description	Default
`bio`	Yes
`url`	Yes
`name`	Yes
`role`	Yes
`website`	Yes
`location`	Yes
`username`	Yes
`languages`	Yes
`modalities`	Yes
`credentials`	Yes
`specialties`	Yes
`license_type`	Yes
`license_state`	Yes
`topics_covered`	Yes
`phone_counseling`	Yes
`online_counseling`	Yes
`years_in_practice`	Yes
`answered_questions`	Yes
`insurance_accepted`	Yes
`therapy_orientation`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedAug 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "answered_questions": {
+      "type": "number"
+    },
+    "bio": {
+      "type": "string"
+    },
+    "credentials": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "insurance_accepted": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "languages": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "license_state": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "license_type": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "location": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "modalities": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "name": {
+      "type": "string"
+    },
+    "online_counseling": {
+      "type": "boolean"
+    },
+    "phone_counseling": {
+      "type": "boolean"
+    },
+    "role": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "specialties": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "therapy_orientation": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "topics_covered": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "url": {
+      "type": "string"
+    },
+    "username": {
+      "type": "string"
+    },
+    "website": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "years_in_practice": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "username",
+    "name",
+    "credentials",
+    "role",
+    "location",
+    "specialties",
+    "languages",
+    "online_counseling",
+    "topics_covered",
+    "url",
+    "therapy_orientation",
+    "modalities",
+    "insurance_accepted",
+    "years_in_practice",
+    "license_type",
+    "license_state",
+    "phone_counseling",
+    "website",
+    "bio",
+    "answered_questions"
+  ],
+  "type": "object"
+}

AddedAug 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description's bar is lower. It adds context that the profile is 'public' and that contact details are intentionally excluded (live on linked page). This gives the agent useful behavioral expectations beyond the annotation without contradiction.

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, front-loaded with main purpose, then a list of profile contents, and a note about contact details. Every word earns its place with zero fluff. Excellent structure for quick scanning.

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?

For a single-parameter tool with an output schema, the description is complete: it lists the main data fields, indicates the source of the username, and states what is NOT included (contact details). The output schema covers return values, so no further explanation is needed. Fully adequate for tool selection and invocation.

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% with 'username' described as 'Expert username from search_experts'. The description repeats this in prose ('by username (as returned by search_experts)') but adds no new semantic detail. Baseline of 3 is appropriate since the schema carries the parameter meaning.

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?

Description clearly states 'Full public profile for one therapist/expert by username' with specific verb 'Get' (from title) and resource. It distinguishes from siblings like search_experts (which returns lists) and get_facility (facilities). Mentions specific fields included (credentials, license type, etc.), so purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says username is 'as returned by search_experts', establishing a prerequisite and workflow. It also notes 'Contact details live on the linked profile page', telling the agent when NOT to use this tool (if contact details are needed). This is clear when-to-use vs alternative guidance.

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

All ChooseHelp Treatment Directory tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool targets a distinct action and resource: search vs. get, experts vs. facilities, and enumerations for specific filter dimensions. There is no overlap or ambiguity between tools like list_browse_categories and list_facility_types because their descriptions clearly differentiate scope.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: get, list, or search followed by a clear object. No style mixing or vague verbs like 'process' or 'do_thing', making the set highly predictable.

Tool Count5/5

Nine tools is well within the ideal range for a directory server. Each tool serves a distinct purpose in the workflow of understanding, browsing, and retrieving facilities/experts, without unnecessary bloat or an overly thin surface.

Completeness5/5

The set covers the full lifecycle of a directory lookup: understanding care levels, enumerating filter values, searching across two entity types, and retrieving full details. Missing operations like create/update/delete are not applicable for a read-only directory, so no critical gaps exist.

Resources

Need Help?