Skip to main content
Glama

GTH Intelligence - Substance Abuse Treatment Finder

by com.gettreatmenthelp
OverviewAdmin

Server Details

Search 12,338 curated, SAMHSA-sourced addiction treatment facilities across all 50 US states.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP
URL
Repository
Crindo2/gth-mcp-server
GitHub Stars
0
Server Listing
GTH Intelligence - Substance Abuse Treatment Finder

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: searching facilities, getting facility details, listing states, and explaining treatment types. No overlap or ambiguity exists.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: get_facility_detail, get_treatment_types, list_states, search_facilities. The verbs and nouns are clear and predictable.

Tool Count5/5

Four tools is well-scoped for a directory-based finder. Each tool earns its place, covering discovery, detailed lookup, domain definitions, and geographic coverage.

Completeness5/5

The toolset covers the full read-only lifecycle: users can discover states with data, search facilities by multiple criteria, retrieve full profiles, and understand treatment types. No obvious gaps for the stated purpose.

Available Tools

4 tools
get_facility_detailGet Facility DetailA
Read-onlyIdempotent
Inspect

Get the full profile of one specific treatment facility: address, phone, programs offered, insurance plans accepted, SAMHSA verification status, and a direct browse URL. Supports partial name matching — returns the best match if multiple facilities contain the query string. Use after search_facilities when the user wants to drill into a named facility.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameYesFull or partial facility name (e.g. 'Betty Ford' or 'Hazelden Betty Ford Center')

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, reducing the burden. The description adds valuable behavioral nuance: 'Supports partial name matching — returns the best match if multiple facilities contain the query string.' This is beyond the annotations, though 'best match' is slightly vague about tie-breaking.

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?

Three sentences with no waste. The first sentence states the core purpose and deliverables, the second explains matching behavior, the third places it in the workflow. Information is front-loaded and each sentence earns its place.

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, read-only, no-output-schema tool, the description covers the purpose, content, matching behavior, and usage context. With annotations handling safety and idempotency, nothing essential is missing for the agent to select and invoke it correctly.

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%, so baseline is 3. The description enriches the 'name' parameter with matching semantics ('Supports partial name matching — returns the best match if multiple facilities contain the query string'), which is not fully expressed in the schema. It explains the behavior, not just the type/format, adding value over structured fields.

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 a specific verb and resource: 'Get the full profile of one specific treatment facility' and enumerates exact contents (address, phone, programs, insurance, SAMHSA status, browse URL). It explicitly distinguishes itself from search_facilities by specifying drill-down intent, making it unmistakable among siblings.

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?

It gives explicit usage context: 'Use after search_facilities when the user wants to drill into a named facility.' This tells the agent exactly when to invoke it and implicitly when not to (i.e., not for searching or listing). It names the alternative tool, satisfying the top guideline bar.

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

get_treatment_typesGet Treatment Type DefinitionsA
Read-onlyIdempotent
Inspect

Get definitions of all treatment program types (Inpatient Rehab, Detox, PHP, IOP, Outpatient, MAT, Counseling, Sober Living) with duration, intensity, and typical fit. Returns markdown-formatted explanations. Use when the user is uncertain which treatment_type to pass to search_facilities, or asks 'what's the difference between X and Y'.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering the safety profile. The description adds useful behavioral context by stating the return format ('markdown-formatted explanations') and that it covers 'all' types. This goes beyond annotations without contradicting them.

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 purpose and action, no redundant phrasing. Every word contributes meaning, making it highly efficient.

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?

Despite having no output schema, the description clarifies what the user gets: definitions, duration, intensity, typical fit, and specific program types. This is complete for a zero-parameter reference tool and requires no further elaboration.

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?

The tool has zero parameters, so there is nothing for the description to add. The baseline for no parameters is 4, and the description correctly omits any parameter details since none exist.

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 starts with a specific verb ('Get definitions') and clear resource ('all treatment program types'), enumerating the specific types. It also implicitly distinguishes from sibling tools like search_facilities by focusing on definitions rather than facility lookup.

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 states when to use the tool: 'Use when the user is uncertain which treatment_type to pass to search_facilities, or asks 'what's the difference between X and Y'.' This provides direct decision guidance and implies the alternative (search_facilities) without needing to name it.

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

list_statesList States with CoverageA
Read-onlyIdempotent
Inspect

List every US state that has treatment facility data in this directory, with per-state facility counts. Returns an array of {state, stateAbbr, count}. Use as a first step when the user's location is unclear, or to discover where coverage exists before calling search_facilities.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the description adds complementary value by disclosing the return shape ('array of {state, stateAbbr, count}') and the fact that it lists only states with data. No contradiction with annotations.

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 the primary action, then return format, then use case. No filler words; every sentence earns its place.

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 zero-parameter listing tool, the description fully conveys the return format and intended usage context. It is self-contained and sufficient for an agent to invoke the tool correctly without additional information.

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?

The tool has zero parameters, so the baseline is 4. The description adds the output structure, which is the only relevant semantic detail. No parameter explanations are 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?

The description clearly states the tool's function: 'List every US state that has treatment facility data in this directory, with per-state facility counts.' It uses a specific verb ('List') and resource ('every US state'), and the scope ('with per-state facility counts') distinguishes it from siblings like search_facilities and get_facility_detail.

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 states when to use: 'Use as a first step when the user's location is unclear, or to discover where coverage exists before calling search_facilities.' It also names the alternative tool (search_facilities), providing clear decision guidance.

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

search_facilitiesSearch Treatment FacilitiesA
Read-onlyIdempotent
Inspect

Search the 12,338 curated, SAMHSA-sourced US addiction treatment facility directory by state, city, treatment type, and insurance. Returns matched facilities with name, city/state, programs offered, insurance accepted, phone, and browse URL. Use this to find candidates — then call get_facility_detail for one facility's full profile. If the user is uncertain about location coverage, call list_states first.

ParametersJSON Schema
NameRequiredDescriptionDefault
cityNoCity name (partial match supported — 'san fran' matches 'San Francisco')
limitNoMax results to return (1-20, default 5)
stateYesUS state name or 2-letter abbreviation (e.g. "California" or "CA"). Required — searches are scoped to one state at a time.
insuranceNoInsurance provider accepted (e.g. "Medicaid", "Aetna", "Blue Cross", "Medicare", "Private Pay"). Partial match supported.
treatment_typeNoType of treatment program. Call get_treatment_types if the user is unsure which applies.

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 and idempotentHint=true, covering the safety profile. The description adds valuable context about the curated directory size and specifies the exact return fields, which goes beyond the schema. It lacks details on pagination or error handling, but the annotations lower the bar, and the added context earns a 4.

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?

Three sentences, each earns its place: the first defines the directory and filters, the second lists return fields, and the third gives usage flow with sibling tools. Highly concise and front-loaded.

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?

Given the read-only/idempotent annotations and a fully descriptive schema, the description covers purpose, return fields, sibling tool flow, and prerequisite conditions. It provides enough context for an agent to select and invoke the tool correctly, even without an output schema.

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 description coverage is 100%, so all five parameters have detailed descriptions with types, defaults, and examples. The tool description recaps search dimensions but adds no new semantics beyond what the schema already provides. Baseline 3 is appropriate.

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 clearly states a specific action ('Search') on a specific resource ('12,338 curated, SAMHSA-sourced US addiction treatment facility directory') with identifiable filters (state, city, treatment type, insurance). It also distinguishes itself from siblings by explicitly directing to get_facility_detail for full profiles and list_states for location coverage.

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?

Explicit guidance is provided: 'Use this to find candidates — then call get_facility_detail for one facility's full profile.' It also instructs when to call list_states first if location coverage is uncertain. This clearly states when to use the tool versus alternatives.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 4 tool updates
    • Changedget_facility_detail1 field changed
      • changedInput schema / properties / name / description
        Previous value: -"Full or partial facility name to search for. Returns the first matching facility. Case-insensitive."New value: +"Full or partial facility name (e.g. 'Betty Ford' or 'Hazelden Betty Ford Center')"
    • Changedget_treatment_types1 field changed
      • removedInput schema / properties / _unused
        Removed value: -{
-  "description": "This tool takes no parameters. Call with an empty arguments object.",
-  "type": "string"
-}
    • Changedlist_states1 field changed
      • removedInput schema / properties / _unused
        Removed value: -{
-  "description": "This tool takes no parameters. Call with an empty arguments object.",
-  "type": "string"
-}
    • Changedsearch_facilities6 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"City name to filter results (e.g. \"Phoenix\", \"New York\"). Case-insensitive partial match."New value: +"City name (partial match supported — 'san fran' matches 'San Francisco')"
      • changedInput schema / properties / insurance / description
        Previous value: -"Insurance provider name to filter by (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Insurance\"). Case-insensitive partial match."New value: +"Insurance provider accepted (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Pay\"). Partial match supported."
      • changedInput schema / properties / limit / description
        Previous value: -"Maximum number of results to return. Range: 1-20, default: 5."New value: +"Max results to return (1-20, default 5)"
      • changedInput schema / properties / state / description
        Previous value: -"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Filters results to facilities in this state."New value: +"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Required — searches are scoped to one state at a time."
      • changedInput schema / properties / treatment_type / description
        Previous value: -"Type of treatment program to filter by. Each facility may offer multiple program types."New value: +"Type of treatment program. Call get_treatment_types if the user is unsure which applies."
      • addedInput schema / required
        Added value: +[
+  "state"
+]
  2. 4 tool updates
    • Changedget_facility_detail1 field changed
      • changedInput schema / properties / name / description
        Previous value: -"Full or partial facility name (e.g. 'Betty Ford' or 'Hazelden Betty Ford Center')"New value: +"Full or partial facility name to search for. Returns the first matching facility. Case-insensitive."
    • Changedget_treatment_types1 field changed
      • addedInput schema / properties / _unused
        Added value: +{
+  "description": "This tool takes no parameters. Call with an empty arguments object.",
+  "type": "string"
+}
    • Changedlist_states1 field changed
      • addedInput schema / properties / _unused
        Added value: +{
+  "description": "This tool takes no parameters. Call with an empty arguments object.",
+  "type": "string"
+}
    • Changedsearch_facilities6 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"City name (partial match supported — 'san fran' matches 'San Francisco')"New value: +"City name to filter results (e.g. \"Phoenix\", \"New York\"). Case-insensitive partial match."
      • changedInput schema / properties / insurance / description
        Previous value: -"Insurance provider accepted (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Pay\"). Partial match supported."New value: +"Insurance provider name to filter by (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Insurance\"). Case-insensitive partial match."
      • changedInput schema / properties / limit / description
        Previous value: -"Max results to return (1-20, default 5)"New value: +"Maximum number of results to return. Range: 1-20, default: 5."
      • changedInput schema / properties / state / description
        Previous value: -"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Required — searches are scoped to one state at a time."New value: +"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Filters results to facilities in this state."
      • changedInput schema / properties / treatment_type / description
        Previous value: -"Type of treatment program. Call get_treatment_types if the user is unsure which applies."New value: +"Type of treatment program to filter by. Each facility may offer multiple program types."
      • removedInput schema / required
        Removed value: -[
-  "state"
-]
  3. 4 tool updates
    • Changedget_facility_detail1 field changed
      • changedInput schema / properties / name / description
        Previous value: -"Full or partial facility name to search for. Returns the first matching facility. Case-insensitive."New value: +"Full or partial facility name (e.g. 'Betty Ford' or 'Hazelden Betty Ford Center')"
    • Changedget_treatment_types1 field changed
      • removedInput schema / properties / _unused
        Removed value: -{
-  "description": "This tool takes no parameters. Call with an empty arguments object.",
-  "type": "string"
-}
    • Changedlist_states1 field changed
      • removedInput schema / properties / _unused
        Removed value: -{
-  "description": "This tool takes no parameters. Call with an empty arguments object.",
-  "type": "string"
-}
    • Changedsearch_facilities6 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"City name to filter results (e.g. \"Phoenix\", \"New York\"). Case-insensitive partial match."New value: +"City name (partial match supported — 'san fran' matches 'San Francisco')"
      • changedInput schema / properties / insurance / description
        Previous value: -"Insurance provider name to filter by (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Insurance\"). Case-insensitive partial match."New value: +"Insurance provider accepted (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Pay\"). Partial match supported."
      • changedInput schema / properties / limit / description
        Previous value: -"Maximum number of results to return. Range: 1-20, default: 5."New value: +"Max results to return (1-20, default 5)"
      • changedInput schema / properties / state / description
        Previous value: -"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Filters results to facilities in this state."New value: +"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Required — searches are scoped to one state at a time."
      • changedInput schema / properties / treatment_type / description
        Previous value: -"Type of treatment program to filter by. Each facility may offer multiple program types."New value: +"Type of treatment program. Call get_treatment_types if the user is unsure which applies."
      • addedInput schema / required
        Added value: +[
+  "state"
+]
  4. 4 tool updates
    • Changedget_facility_detail1 field changed
      • changedInput schema / properties / name / description
        Previous value: -"Full or partial facility name (e.g. 'Betty Ford' or 'Hazelden Betty Ford Center')"New value: +"Full or partial facility name to search for. Returns the first matching facility. Case-insensitive."
    • Changedget_treatment_types1 field changed
      • addedInput schema / properties / _unused
        Added value: +{
+  "description": "This tool takes no parameters. Call with an empty arguments object.",
+  "type": "string"
+}
    • Changedlist_states1 field changed
      • addedInput schema / properties / _unused
        Added value: +{
+  "description": "This tool takes no parameters. Call with an empty arguments object.",
+  "type": "string"
+}
    • Changedsearch_facilities6 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"City name (partial match supported — 'san fran' matches 'San Francisco')"New value: +"City name to filter results (e.g. \"Phoenix\", \"New York\"). Case-insensitive partial match."
      • changedInput schema / properties / insurance / description
        Previous value: -"Insurance provider accepted (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Pay\"). Partial match supported."New value: +"Insurance provider name to filter by (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Insurance\"). Case-insensitive partial match."
      • changedInput schema / properties / limit / description
        Previous value: -"Max results to return (1-20, default 5)"New value: +"Maximum number of results to return. Range: 1-20, default: 5."
      • changedInput schema / properties / state / description
        Previous value: -"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Required — searches are scoped to one state at a time."New value: +"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Filters results to facilities in this state."
      • changedInput schema / properties / treatment_type / description
        Previous value: -"Type of treatment program. Call get_treatment_types if the user is unsure which applies."New value: +"Type of treatment program to filter by. Each facility may offer multiple program types."
      • removedInput schema / required
        Removed value: -[
-  "state"
-]
  5. 4 tool updates
    • Changedget_facility_detail1 field changed
      • changedInput schema / properties / name / description
        Previous value: -"Full or partial facility name to search for. Returns the first matching facility. Case-insensitive."New value: +"Full or partial facility name (e.g. 'Betty Ford' or 'Hazelden Betty Ford Center')"
    • Changedget_treatment_types1 field changed
      • removedInput schema / properties / _unused
        Removed value: -{
-  "description": "This tool takes no parameters. Call with an empty arguments object.",
-  "type": "string"
-}
    • Changedlist_states1 field changed
      • removedInput schema / properties / _unused
        Removed value: -{
-  "description": "This tool takes no parameters. Call with an empty arguments object.",
-  "type": "string"
-}
    • Changedsearch_facilities6 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"City name to filter results (e.g. \"Phoenix\", \"New York\"). Case-insensitive partial match."New value: +"City name (partial match supported — 'san fran' matches 'San Francisco')"
      • changedInput schema / properties / insurance / description
        Previous value: -"Insurance provider name to filter by (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Insurance\"). Case-insensitive partial match."New value: +"Insurance provider accepted (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Pay\"). Partial match supported."
      • changedInput schema / properties / limit / description
        Previous value: -"Maximum number of results to return. Range: 1-20, default: 5."New value: +"Max results to return (1-20, default 5)"
      • changedInput schema / properties / state / description
        Previous value: -"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Filters results to facilities in this state."New value: +"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Required — searches are scoped to one state at a time."
      • changedInput schema / properties / treatment_type / description
        Previous value: -"Type of treatment program to filter by. Each facility may offer multiple program types."New value: +"Type of treatment program. Call get_treatment_types if the user is unsure which applies."
      • addedInput schema / required
        Added value: +[
+  "state"
+]
  6. 4 tool updates
    • Changedget_facility_detail1 field changed
      • changedInput schema / properties / name / description
        Previous value: -"Full or partial facility name (e.g. 'Betty Ford' or 'Hazelden Betty Ford Center')"New value: +"Full or partial facility name to search for. Returns the first matching facility. Case-insensitive."
    • Changedget_treatment_types1 field changed
      • addedInput schema / properties / _unused
        Added value: +{
+  "description": "This tool takes no parameters. Call with an empty arguments object.",
+  "type": "string"
+}
    • Changedlist_states1 field changed
      • addedInput schema / properties / _unused
        Added value: +{
+  "description": "This tool takes no parameters. Call with an empty arguments object.",
+  "type": "string"
+}
    • Changedsearch_facilities6 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"City name (partial match supported — 'san fran' matches 'San Francisco')"New value: +"City name to filter results (e.g. \"Phoenix\", \"New York\"). Case-insensitive partial match."
      • changedInput schema / properties / insurance / description
        Previous value: -"Insurance provider accepted (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Pay\"). Partial match supported."New value: +"Insurance provider name to filter by (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Insurance\"). Case-insensitive partial match."
      • changedInput schema / properties / limit / description
        Previous value: -"Max results to return (1-20, default 5)"New value: +"Maximum number of results to return. Range: 1-20, default: 5."
      • changedInput schema / properties / state / description
        Previous value: -"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Required — searches are scoped to one state at a time."New value: +"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Filters results to facilities in this state."
      • changedInput schema / properties / treatment_type / description
        Previous value: -"Type of treatment program. Call get_treatment_types if the user is unsure which applies."New value: +"Type of treatment program to filter by. Each facility may offer multiple program types."
      • removedInput schema / required
        Removed value: -[
-  "state"
-]
  7. 4 tool updates
    • Changedget_facility_detail1 field changed
      • changedInput schema / properties / name / description
        Previous value: -"Full or partial facility name to search for. Returns the first matching facility. Case-insensitive."New value: +"Full or partial facility name (e.g. 'Betty Ford' or 'Hazelden Betty Ford Center')"
    • Changedget_treatment_types1 field changed
      • removedInput schema / properties / _unused
        Removed value: -{
-  "description": "This tool takes no parameters. Call with an empty arguments object.",
-  "type": "string"
-}
    • Changedlist_states1 field changed
      • removedInput schema / properties / _unused
        Removed value: -{
-  "description": "This tool takes no parameters. Call with an empty arguments object.",
-  "type": "string"
-}
    • Changedsearch_facilities6 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"City name to filter results (e.g. \"Phoenix\", \"New York\"). Case-insensitive partial match."New value: +"City name (partial match supported — 'san fran' matches 'San Francisco')"
      • changedInput schema / properties / insurance / description
        Previous value: -"Insurance provider name to filter by (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Insurance\"). Case-insensitive partial match."New value: +"Insurance provider accepted (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Pay\"). Partial match supported."
      • changedInput schema / properties / limit / description
        Previous value: -"Maximum number of results to return. Range: 1-20, default: 5."New value: +"Max results to return (1-20, default 5)"
      • changedInput schema / properties / state / description
        Previous value: -"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Filters results to facilities in this state."New value: +"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Required — searches are scoped to one state at a time."
      • changedInput schema / properties / treatment_type / description
        Previous value: -"Type of treatment program to filter by. Each facility may offer multiple program types."New value: +"Type of treatment program. Call get_treatment_types if the user is unsure which applies."
      • addedInput schema / required
        Added value: +[
+  "state"
+]
  8. 4 tool updates
    • Changedget_facility_detail1 field changed
      • changedInput schema / properties / name / description
        Previous value: -"Full or partial facility name (e.g. 'Betty Ford' or 'Hazelden Betty Ford Center')"New value: +"Full or partial facility name to search for. Returns the first matching facility. Case-insensitive."
    • Changedget_treatment_types1 field changed
      • addedInput schema / properties / _unused
        Added value: +{
+  "description": "This tool takes no parameters. Call with an empty arguments object.",
+  "type": "string"
+}
    • Changedlist_states1 field changed
      • addedInput schema / properties / _unused
        Added value: +{
+  "description": "This tool takes no parameters. Call with an empty arguments object.",
+  "type": "string"
+}
    • Changedsearch_facilities6 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"City name (partial match supported — 'san fran' matches 'San Francisco')"New value: +"City name to filter results (e.g. \"Phoenix\", \"New York\"). Case-insensitive partial match."
      • changedInput schema / properties / insurance / description
        Previous value: -"Insurance provider accepted (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Pay\"). Partial match supported."New value: +"Insurance provider name to filter by (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Insurance\"). Case-insensitive partial match."
      • changedInput schema / properties / limit / description
        Previous value: -"Max results to return (1-20, default 5)"New value: +"Maximum number of results to return. Range: 1-20, default: 5."
      • changedInput schema / properties / state / description
        Previous value: -"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Required — searches are scoped to one state at a time."New value: +"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Filters results to facilities in this state."
      • changedInput schema / properties / treatment_type / description
        Previous value: -"Type of treatment program. Call get_treatment_types if the user is unsure which applies."New value: +"Type of treatment program to filter by. Each facility may offer multiple program types."
      • removedInput schema / required
        Removed value: -[
-  "state"
-]
  9. 2 tool updates
    • Changedget_facility_detail1 field changed
      • changedInput schema / properties / name / description
        Previous value: -"Full or partial facility name"New value: +"Full or partial facility name (e.g. 'Betty Ford' or 'Hazelden Betty Ford Center')"
    • Changedsearch_facilities6 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"City name"New value: +"City name (partial match supported — 'san fran' matches 'San Francisco')"
      • changedInput schema / properties / insurance / description
        Previous value: -"Insurance provider (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Pay\")"New value: +"Insurance provider accepted (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Pay\"). Partial match supported."
      • changedInput schema / properties / limit / description
        Previous value: -"Results to return (1-20, default 5)"New value: +"Max results to return (1-20, default 5)"
      • changedInput schema / properties / state / description
        Previous value: -"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\")"New value: +"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Required — searches are scoped to one state at a time."
      • changedInput schema / properties / treatment_type / description
        Previous value: -"Type of treatment program"New value: +"Type of treatment program. Call get_treatment_types if the user is unsure which applies."
      • addedInput schema / required
        Added value: +[
+  "state"
+]
  10. 4 tool updates
    • Changedget_facility_detail1 field changed
      • changedInput schema / properties / name / description
        Previous value: -"Full or partial facility name to search for. Returns the first matching facility. Case-insensitive."New value: +"Full or partial facility name"
    • Changedget_treatment_types1 field changed
      • removedInput schema / properties / _unused
        Removed value: -{
-  "description": "This tool takes no parameters. Call with an empty arguments object.",
-  "type": "string"
-}
    • Changedlist_states1 field changed
      • removedInput schema / properties / _unused
        Removed value: -{
-  "description": "This tool takes no parameters. Call with an empty arguments object.",
-  "type": "string"
-}
    • Changedsearch_facilities5 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"City name to filter results (e.g. \"Phoenix\", \"New York\"). Case-insensitive partial match."New value: +"City name"
      • changedInput schema / properties / insurance / description
        Previous value: -"Insurance provider name to filter by (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Insurance\"). Case-insensitive partial match."New value: +"Insurance provider (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Pay\")"
      • changedInput schema / properties / limit / description
        Previous value: -"Maximum number of results to return. Range: 1-20, default: 5."New value: +"Results to return (1-20, default 5)"
      • changedInput schema / properties / state / description
        Previous value: -"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Filters results to facilities in this state."New value: +"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\")"
      • changedInput schema / properties / treatment_type / description
        Previous value: -"Type of treatment program to filter by. Each facility may offer multiple program types."New value: +"Type of treatment program"
  11. 4 tool updates
    • Changedget_facility_detail1 field changed
      • changedInput schema / properties / name / description
        Previous value: -"Full or partial facility name"New value: +"Full or partial facility name to search for. Returns the first matching facility. Case-insensitive."
    • Changedget_treatment_types1 field changed
      • addedInput schema / properties / _unused
        Added value: +{
+  "description": "This tool takes no parameters. Call with an empty arguments object.",
+  "type": "string"
+}
    • Changedlist_states1 field changed
      • addedInput schema / properties / _unused
        Added value: +{
+  "description": "This tool takes no parameters. Call with an empty arguments object.",
+  "type": "string"
+}
    • Changedsearch_facilities5 fields changed
      • changedInput schema / properties / city / description
        Previous value: -"City name"New value: +"City name to filter results (e.g. \"Phoenix\", \"New York\"). Case-insensitive partial match."
      • changedInput schema / properties / insurance / description
        Previous value: -"Insurance provider (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Pay\")"New value: +"Insurance provider name to filter by (e.g. \"Medicaid\", \"Aetna\", \"Blue Cross\", \"Medicare\", \"Private Insurance\"). Case-insensitive partial match."
      • changedInput schema / properties / limit / description
        Previous value: -"Results to return (1-20, default 5)"New value: +"Maximum number of results to return. Range: 1-20, default: 5."
      • changedInput schema / properties / state / description
        Previous value: -"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\")"New value: +"US state name or 2-letter abbreviation (e.g. \"California\" or \"CA\"). Filters results to facilities in this state."
      • changedInput schema / properties / treatment_type / description
        Previous value: -"Type of treatment program"New value: +"Type of treatment program to filter by. Each facility may offer multiple program types."
  12. 4 tool updates
    • First observedget_facility_detail
    • First observedget_treatment_types
    • First observedlist_states
    • First observedsearch_facilities

Frequently Asked Questions

Discussions

No comments yet. Be the first to start the discussion!

Login with GitHub to comment

Related MCP Connectors

Related MCP Servers

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.

Resources