Skip to main content
Glama

mental-health-care

by com.emorahealth
OverviewDiscussionsAdmin

Find a Clinician

find_provider
Read-only

The canonical 'find a clinician' tool. Returns providers who fit the filters, ranked best first by Emora's production matching algorithm (rankTherapist), ten at a time by default with no cap: use limit and offset to page, and total_candidates to see how many exist: each concern maps to weighted specialties; each provider's specialties score against that map; approach / language / rating / availability layer on top. Pass concerns[] for a clinical match; omit them for a logistical (availability + rating) ranking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many ranked matches to return. Defaults to 10. There is no maximum: pass total_candidates from a previous call to get every match.
stateYes
offsetNoHow many ranked matches to skip. Pass next_offset from a previous call to get the next page.
concernsNoConcern IDs from the curated enum (see ConcernId). Pass 1-3 for best results — too many concerns dilute the score.
insuranceNo
client_ageNo
continuationNoToken from a previous find_provider call. Re-applies prior client profile; new args override.
appointment_typeYes
preferred_genderNoProvider gender preference (e.g. 'female','male','non-binary').
preferred_languageNoNon-English language the provider should speak.
preferred_approachesNoTherapy modalities the user prefers (e.g. ["cbt","dbt","playTherapy"]). Bumps the score for providers whose approaches list includes these.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "How many ranked matches to return. Defaults to 10. There is no maximum: pass total_candidates from a previous call to get every match.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "How many ranked matches to skip. Pass next_offset from a previous call to get the next page.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / insurance / enum
      Previous value: -[
-  "Cash Pay",
-  "Aetna",
-  "Anthem Blue Cross",
-  "Baylor Scott & White",
-  "Blue Cross Blue Shield",
-  "ChampVA",
-  "Cigna",
-  "Florida Blue",
-  "Magellan",
-  "Medical Mutual",
-  "United Healthcare",
-  "Optum",
-  "Oscar",
-  "Tricare",
-  "Tricare West",
-  "UMR"
-]New value: +[
+  "Cash Pay",
+  "Aetna",
+  "Anthem Blue Cross",
+  "Blue Cross Blue Shield",
+  "ChampVA",
+  "Cigna",
+  "Florida Blue",
+  "Magellan",
+  "Medical Mutual",
+  "United Healthcare",
+  "Optum",
+  "Oscar",
+  "Tricare",
+  "Tricare West",
+  "UMR"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / state / enum
      Previous value: -[
-  "Florida",
-  "Texas",
-  "Illinois",
-  "North Carolina",
-  "Ohio",
-  "Missouri",
-  "Arizona",
-  "Georgia",
-  "Wisconsin",
-  "South Carolina",
-  "Indiana"
-]New value: +[
+  "Florida",
+  "Texas",
+  "Illinois",
+  "North Carolina",
+  "Georgia",
+  "Ohio",
+  "Missouri",
+  "Arizona",
+  "Wisconsin",
+  "South Carolina",
+  "Indiana"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / insurance / enum
      Previous value: -[
-  "Cash Pay",
-  "Aetna",
-  "Anthem Blue Cross",
-  "Baylor Scott & White",
-  "Blue Cross Blue Shield",
-  "ChampVA",
-  "Cigna",
-  "Florida Blue",
-  "Magellan",
-  "United Healthcare",
-  "Optum",
-  "Oscar",
-  "Tricare",
-  "Tricare West",
-  "UMR"
-]New value: +[
+  "Cash Pay",
+  "Aetna",
+  "Anthem Blue Cross",
+  "Baylor Scott & White",
+  "Blue Cross Blue Shield",
+  "ChampVA",
+  "Cigna",
+  "Florida Blue",
+  "Magellan",
+  "Medical Mutual",
+  "United Healthcare",
+  "Optum",
+  "Oscar",
+  "Tricare",
+  "Tricare West",
+  "UMR"
+]
  5. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  6. Changed1 schema field changed
    • changedInput schema / properties / concerns / items / enum
      Previous value: -[
-  "sep-anxiety",
-  "gad",
-  "social-anxiety",
-  "specific-phobia",
-  "panic-attacks",
-  "depression",
-  "bipolar",
-  "irritability",
-  "grief",
-  "adhd",
-  "odd",
-  "conduct",
-  "impulsivity",
-  "autism",
-  "speech-delay",
-  "motor-delay",
-  "learning-disability",
-  "sleep-disorder",
-  "peer-issues",
-  "life-transitions",
-  "family-changes",
-  "relocation",
-  "social-stress",
-  "relationship-issues",
-  "build-confidence",
-  "grow-faith",
-  "mindfulness",
-  "personal-values",
-  "resilience",
-  "self-compassion",
-  "unsure",
-  "other"
-]New value: +[
+  "parenting-stress",
+  "sep-anxiety",
+  "gad",
+  "social-anxiety",
+  "specific-phobia",
+  "panic-attacks",
+  "depression",
+  "bipolar",
+  "irritability",
+  "grief",
+  "adhd",
+  "odd",
+  "conduct",
+  "impulsivity",
+  "autism",
+  "speech-delay",
+  "motor-delay",
+  "learning-disability",
+  "sleep-disorder",
+  "peer-issues",
+  "life-transitions",
+  "family-changes",
+  "relocation",
+  "social-stress",
+  "relationship-issues",
+  "build-confidence",
+  "grow-faith",
+  "mindfulness",
+  "personal-values",
+  "resilience",
+  "self-compassion",
+  "unsure",
+  "other"
+]
  7. Changed1 schema field changed
    • changedInput schema / properties / state / enum
      Previous value: -[
-  "Florida",
-  "Texas",
-  "Illinois",
-  "North Carolina",
-  "Ohio",
-  "Missouri",
-  "Arizona",
-  "Georgia",
-  "Wisconsin",
-  "South Carolina"
-]New value: +[
+  "Florida",
+  "Texas",
+  "Illinois",
+  "North Carolina",
+  "Ohio",
+  "Missouri",
+  "Arizona",
+  "Georgia",
+  "Wisconsin",
+  "South Carolina",
+  "Indiana"
+]
  8. Changed2 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / appointment_type / enum
      Previous value: -[
-  "354092",
-  "446840",
-  "465593",
-  "446841",
-  "449671"
-]New value: +[
+  "354092",
+  "446840",
+  "446841",
+  "449671",
+  "465593"
+]
  9. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, it reveals the production matching algorithm (rankTherapist), the default page size with no cap, paging mechanics, concern-to-specialty weighting, and the layering of approach/language/rating/availability. This gives the agent a precise mental model of how results are produced and is not contradicted by annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The content is dense and informative but delivered as one long run-on sentence with colon-separated clauses. It front-loads the core purpose well, but the layout is hard to parse at a glance; splitting into two or three sentences would improve readability without losing information.

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 an 11-parameter tool with no output schema, the description adequately covers ranking, paging, the two ranking modes, and how filters contribute. It does not explicitly describe the full response shape beyond total_candidates, and it omits mention of next_offset (present in the schema), but an agent can still invoke the tool correctly based on the provided guidance.

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?

With 64% schema description coverage, the schema handles many parameters, but the description adds meaning beyond it: it explains how concerns map to weighted specialties, how limit/offset interact with default paging, and it introduces total_candidates. The remaining undocumented params (state, appointment_type, insurance, client_age) are reasonably self-evident from their enums/names.

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?

The description opens with 'The canonical find a clinician tool' and states it 'Returns providers who fit the filters, ranked best first', giving a specific verb, resource, and behavior. It distinguishes itself from siblings by naming the ranking algorithm and paging semantics, so an agent knows exactly what this tool does.

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 provides clear usage context: 'Pass concerns[] for a clinical match; omit them for a logistical (availability + rating) ranking.' It also explains when to page using limit/offset and total_candidates. However, it does not explicitly contrast with sibling tools like check_availability or search_content, relying on 'canonical' rather than naming alternatives.

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

All mental-health-care 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