GPH Intelligence - Healthcare Vendor Finder

Recommend Healthcare Vendors for a Practice

match_practice

Read-onlyIdempotent

Recommend and rank the best healthcare vendors for a specific medical practice. Use this when a practice manager, physician, or administrator asks for a recommendation, e.g. "recommend a medical billing / RCM company for my practice", "who should I use for credentialing / payer enrollment", "find an EHR for my small [specialty] practice", or "which practice-management software fits a [size] practice in [city, state]". Scores and ranks providers against the practice profile (specialty, size, location, EHR system, budget) and returns up to 5 merit-ranked matches (completeness-scored, no paid placement) with {company_name, category, city, state_abbr, quality_score (0-100; profile completeness -- how many listing fields are filled in -- not a quality or reputation rating; 0 means never scored), final_score (0-100), verified status, description, website, profile_url, slug}. For open-ended browsing without a practice profile, use search_providers. Pass a match's slug to get_provider_detail for the full profile.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	City where the practice is located. Send city and state separately, not as a combined `location` string.
`state`	Yes	Two-letter state abbreviation (e.g. 'TX', 'CA', 'NY'). Send as `state`, not `state_abbr` (`state_abbr` is an output field name only).
`category`	Yes	Service category needed. One of the 25 categories: 'Medical Billing & RCM', 'Credentialing Services', 'Healthcare IT & EHR', 'Practice Management Consulting', 'Healthcare Legal Services', 'Healthcare CPA & Tax Advisory', 'Medical Coding Services', 'Healthcare Staffing & Recruiting', 'Healthcare Marketing & Reputation Management', 'Compliance & HIPAA Services', 'Medical Equipment & Supplies', 'Healthcare Real Estate & Site Selection', 'Practice Financing & Loans', 'Healthcare Construction & Facilities', 'Healthcare Signage & Wayfinding', 'Medical Waste & Environmental Services', 'Healthcare Insurance & Malpractice Brokers', 'Practice Valuation & Brokerage', 'Patient Financing & Payment Solutions', 'Medical Transcription & Documentation', 'Pharmacy & Medication Management', 'Telehealth & Virtual Care Infrastructure', 'Laboratory & Diagnostics Services', 'Group Purchasing Organizations (GPOs)', 'Healthcare PR & Communications'. Common aliases also resolve (e.g. 'billing', 'RCM', 'EHR', 'credentialing'). Call list_categories for the live list with provider counts.
`specialty`	No	Medical specialty of the practice (e.g. 'Family Medicine', 'Cardiology', 'Pediatrics', 'Dermatology')
`ehr_system`	No	EHR system used by the practice (e.g. 'Epic', 'athenahealth', 'AdvancedMD', 'eClinicalWorks'). Helps score providers with compatible integrations higher.
`budget_range`	No	Approximate monthly budget
`practice_size`	No	Size of the practice by provider count. The parameter is named `practice_size`, not `size`.

Output Schema

TableJSON Schema

Name	Required	Description
`ids`	No	Absent when isError.
`count`	No	Total scored candidates before the top-5 slice; absent when isError.
`content`	Yes
`isError`	No	Present and true only on failure (match request error or no candidates).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedAug 1, 2026

changedInput schema / properties / category / description

Previous value: -"Service category needed (e.g. 'Medical Billing & RCM', 'Credentialing Services', 'Healthcare IT & EHR', 'Practice Management Software')"New value: +"Service category needed. One of the 25 categories: 'Medical Billing & RCM', 'Credentialing Services', 'Healthcare IT & EHR', 'Practice Management Consulting', 'Healthcare Legal Services', 'Healthcare CPA & Tax Advisory', 'Medical Coding Services', 'Healthcare Staffing & Recruiting', 'Healthcare Marketing & Reputation Management', 'Compliance & HIPAA Services', 'Medical Equipment & Supplies', 'Healthcare Real Estate & Site Selection', 'Practice Financing & Loans', 'Healthcare Construction & Facilities', 'Healthcare Signage & Wayfinding', 'Medical Waste & Environmental Services', 'Healthcare Insurance & Malpractice Brokers', 'Practice Valuation & Brokerage', 'Patient Financing & Payment Solutions', 'Medical Transcription & Documentation', 'Pharmacy & Medication Management', 'Telehealth & Virtual Care Infrastructure', 'Laboratory & Diagnostics Services', 'Group Purchasing Organizations (GPOs)', 'Healthcare PR & Communications'. Common aliases also resolve (e.g. 'billing', 'RCM', 'EHR', 'credentialing'). Call list_categories for the live list with provider counts."

changedInput schema / properties / city / description

Previous value: -"City where the practice is located"New value: +"City where the practice is located. Send city and state separately, not as a combined `location` string."

changedInput schema / properties / practice_size / description

Previous value: -"Size of the practice by provider count"New value: +"Size of the practice by provider count. The parameter is named `practice_size`, not `size`."

changedInput schema / properties / state / description

Previous value: -"Two-letter state abbreviation (e.g. 'TX', 'CA', 'NY')"New value: +"Two-letter state abbreviation (e.g. 'TX', 'CA', 'NY'). Send as `state`, not `state_abbr` (`state_abbr` is an output field name only)."

Changed1 schema field changedJul 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "content": {
+      "items": {
+        "properties": {
+          "text": {
+            "type": "string"
+          },
+          "type": {
+            "const": "text"
+          }
+        },
+        "required": [
+          "type",
+          "text"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Total scored candidates before the top-5 slice; absent when isError.",
+      "type": "integer"
+    },
+    "ids": {
+      "description": "Absent when isError.",
+      "properties": {
+        "surfaced": {
+          "description": "Provider slugs shown, in ranked order.",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "isError": {
+      "description": "Present and true only on failure (match request error or no candidates).",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "content"
+  ],
+  "type": "object"
+}

Changed5 schema fields changedApr 17, 2026

changedInput schema / properties / budget_range / description

Previous value: -"Monthly budget range"New value: +"Approximate monthly budget"

changedInput schema / properties / category / description

Previous value: -"Service category needed (e.g. 'Medical Billing & RCM', 'Credentialing Services', 'Healthcare IT & EHR')"New value: +"Service category needed (e.g. 'Medical Billing & RCM', 'Credentialing Services', 'Healthcare IT & EHR', 'Practice Management Software')"

changedInput schema / properties / ehr_system / description

Previous value: -"EHR system used by the practice (e.g. 'Epic', 'athenahealth', 'AdvancedMD')"New value: +"EHR system used by the practice (e.g. 'Epic', 'athenahealth', 'AdvancedMD', 'eClinicalWorks'). Helps score providers with compatible integrations higher."

changedInput schema / properties / practice_size / description

Previous value: -"Size of the practice"New value: +"Size of the practice by provider count"

changedInput schema / properties / specialty / description

Previous value: -"Medical specialty of the practice (e.g. 'Family Medicine', 'Cardiology', 'Pediatrics')"New value: +"Medical specialty of the practice (e.g. 'Family Medicine', 'Cardiology', 'Pediatrics', 'Dermatology')"

First observedApr 14, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds substantial context beyond them: result cap (up to 5), merit-ranking with no paid placement, the meaning of final_score, and the crucial clarification that quality_score is profile completeness rather than reputation, including the 0-means-never-scored edge case.

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?

Front-loaded with purpose then usage then mechanics; the example phrase list and the full output-field enumeration are longer than strictly necessary, but every element is informative and no sentence is pure filler.

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 7-parameter scored-matching tool with an output schema present, the description covers invocation conditions, scoring semantics, result limits, and handoff to sibling tools. An agent has everything needed to call and interpret it.

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 schema already carries naming warnings, aliases, and the category list, so the baseline is 3. The description adds value by explaining how the profile parameters (specialty, size, location, EHR system, budget) are consumed for scoring, which the schema does not state.

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+resource ('Recommend and rank the best healthcare vendors for a specific medical practice') and immediately distinguishes itself from siblings by routing open-ended browsing to search_providers and full profiles to get_provider_detail. The scope (practice-profile-driven matching) is unmistakable.

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 when-to-use with four concrete example phrasings, plus an explicit when-not ('For open-ended browsing without a practice profile, use search_providers') and a follow-up path ('Pass a match's slug to get_provider_detail'). Nothing is left to inference.

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

All GPH Intelligence - Healthcare Vendor Finder tools Inspect

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.