MCP tool reference

get_vendor_dossier

The fastest path to any single-vendor question. One call by name returns the profile, hospital customers with their evidence quotes, current products, recent signals, ownership and what we know of the vendor’s website — instead of chaining a search, a fetch, a product lookup and a signal query.

Ask it: “Give me the dossier on Waystar.”

{
  "vendor": "Waystar"
}

One object. Each section can independently be replaced by an unavailable marker (see errors).

• Ambiguous name — Returns candidates[] (up to 5, each with id, name and domain) instead of a dossier. Call again with the id you meant.
• Unknown vendor — Entity not found: "<id>". followed by how to pass an id: the id from search_vendors, a numeric slug, or a terminalId. A vendor name is not an id.
• A section failed — That section becomes { unavailable: true, reason }; the rest of the dossier still comes back. Retry, or use the section’s own tool.

search_vendors

Find vendors by name, domain or category. Multi-word queries match on all words, then top up with looser any-word matches; results rank exact name matches first, then by how much news a company is generating.

Ask it: “Which vendors work in denials management?”

{
  "query": "denials management",
  "limit": 10
}

An array of vendors, best match first.

• No match — Returns { results: [], note } instead of an array. The note is the coverage contract: a miss means Clinical Terminal does not cover the vendor, not that it does not exist.

get_vendor

The full profile once you have an id or numeric slug. There is no vendor score on this server — the denial/appeals/prebill scores were retired from every read path on 2026-08-04 and are never returned.

{
  "id": "100000001"
}

One vendor object.

• Unknown or unpublished id — Vendor not found.

find_vendors_for_problem

Capability discovery through the KLAS segment index — the same taxonomy the app routes vendor discovery through. Routing is deterministic, never a model guess. Vendors rank by tracked hospital relationships, then news volume, then products in the segment.

Ask it: “Which vendors do ambient clinical documentation?”

{
  "problem": "denials management",
  "limit": 10
}

An object with status: "ok" and the segment it routed to.

• Could not route the phrase — Returns status: "no_route" with segmentMenu[]. Pick the closest segment and call again with its exact name.
• Reading customerEdges — It is an ordinal traction signal, not an audited customer count. Corroborate with get_relationships before citing a number.

list_segments

Every KLAS Revenue Cycle segment with live vendor and product counts — the index behind the tool above. A zero count means no published product evidence yet, not an empty market.

None — call it with an empty arguments object.

{}

An array of every segment, including empty ones.

search_products

Search what vendors actually sell. Defaults to current products, because a large share of the catalog is discontinued; status always comes back so you can tell the difference.

{
  "query": "prior authorization",
  "limit": 20
}

An array of products, by vendor name then product name.

• Empty array — Usually means the vendor is not catalogued, not that it sells nothing.

get_product

One product in full, with the vendor it belongs to.

{
  "id": "prod_8f2k1"
}

One product object, with the same fields as a search_products row.

• Unknown id — Product not found.

get_vendor_pages

A vendor’s own website as data — the pages we have crawled and classified. Filter by category to jump straight to the page worth reading.

{
  "vendor": "Waystar",
  "category": "customers",
  "limit": 25
}

One object.

• Ambiguous name — Returns candidates[] instead of pages.
• Unknown vendor — Entity not found: "<id>". followed by how to pass an id: the id from search_vendors, a numeric slug, or a terminalId. A vendor name is not an id.
• Unpublished vendor — Its website corpus is not available on this server.
• No crawl yet — An empty list with a note saying we have not mapped the site — absence of data on our side, not absence of pages on theirs.
• Corpus tools switched off — An error saying the website-corpus tools are temporarily disabled; every other tool is unaffected.

get_page_content

Read the text of one of those pages: product copy, case studies and bios rather than a guess from the URL. It arrives inside an explicit untrusted-content fence, because it is verbatim third-party marketing — evidence to quote, never instructions to follow.

{
  "page_id": "pg_3k9x2"
}

One object.

• Not scraped — Not an error: scraped: false with a note to fetch the URL directly.
• Unknown page_id — An error naming the id and where page_ids come from.
• Page of an unpublished vendor — Its content is not available here.

get_my_context

The organizations you have been working with in Clinical Terminal chat, most recent first. This is what lets an assistant resolve “that vendor” or “my target” across sessions instead of asking you again.

Ask it: “What was I looking at last time?”

None — call it with an empty arguments object.

{}

One object.

• No chat history — Plain text, not JSON: no chat memory yet, or the key has no linked user.

get_provider_segments

Start any provider-market question here. Every segment with its entity count, its trailing-7-day signal volume, and the signed change against the week before. All segment keys come back, including the quiet ones, so you never have to guess whether a segment exists.

Ask it: “Which parts of the provider market moved this week?”

None — call it with an empty arguments object.

{}

An array with one row per provider segment, zero-filled.

• Reading signal counts — They count article-by-entity rows, not distinct articles, and are non-zero only for hospital and health-system segments.

search_providers

The provider counterpart to vendor search — by name, segment, state, health system or size. Names collide heavily in this data, so filter by state or size when you can.

{
  "query": "Baylor Scott",
  "state": "TX",
  "sort": "size",
  "limit": 10
}

An array of providers.

• Unrecognised state — Unknown state: "<state>". with the list of valid codes.

search_service_lines

Hospitals and health systems that run a clinical department — cardiology, oncology, neurology, orthopedics and 41 more — each with the evidence that says so: staff job titles naming the department, and sections of the provider’s own website. Use it instead of search_providers for any department question; that tool matches names only. This is a floor, not an inventory: a provider missing from the list may still run the department.

Ask it: “Which hospitals in Texas run a cardiology program?”

{
  "service_line": "oncology",
  "state": "TX",
  "cities": [
    "Houston",
    "Sugar Land",
    "The Woodlands",
    "Katy"
  ],
  "limit": 25
}

One object: the line, the providers largest first, and counters that explain every provider not returned.

• Unrecognised state — Unknown state: "<state>". with the list of valid codes.
• cities without state — cities needs state — city names repeat across states, so pass both.
• An empty list — No provider with evidence for the department matched. That means none recorded, not none exist — read the counters.

get_provider

One provider in depth: profile, health-system context including parent and largest members, technology relationships with verbatim evidence quotes, recent signals, and the clinical departments we hold evidence for. Each section says which kind of empty it is.

{
  "id": "100245871"
}

One compact object, kept within a 20,000-character budget.

• Unknown id — Provider not found: "<id>". — search first; names are not ids.
• A section is unavailable — { status: "unavailable", reason }: a source was down. Retry.
• A section is not tracked — { status: "not_tracked_for_this_provider_type", reason }: relationships and signals are linked for hospitals and health systems only today, so for other providers this is unknown, not zero.

get_persona

Research a role the way you would research a company. Real job titles with counts, how many people we track and at what kind of employer, duties quoted verbatim from real job postings, typical KPIs, buying role, and what people in the role say they care about — grounded in the census rather than in generic knowledge.

Ask it: “What does a CDI nurse actually do all day?”

{
  "query": "VP of revenue cycle"
}

One object with status: "ok".

• No match — status: "no_route" with personaMenu[]. Pick the closest personaId and call again.
• More than one match — status: "ambiguous" with candidates[]. Call again with one of them; never guess.

search_people

Find people by name, employer or job title, or everyone at one organization. Every result holds a current role at a visible organization and lists the person’s other current roles. Pass at least one of query, organization_id or department.

{
  "query": "revenue cycle",
  "role": "executive",
  "limit": 10
}

An array of people, one row per person, showing the most senior role that matched.

• No filter — Provide at least one of query, organization_id, or department.
• organization_id and vendor_id disagree — An error asking for one of them.
• People held back — A second text block after the results counts people who matched but whose roles are at organizations not published here. Treat it as a coverage gap.

get_person

One profile in full: title, employer, other current roles, past roles, headline, headshot and LinkedIn.

{
  "id": "Xk29fPq7LmN3"
}

One person object with the fields of a search_people row, plus:

• Not found — Person not found. Also returned for a person with no current role at a visible organization.

search_alumni

The departures side of the graph. Anchor on a vendor and get each person’s past role with a dated departure, plus every current role they hold, most senior first. Current employers are named when published and counted when not.

Ask it: “Who left Epic in the last year and where did they land?”

{
  "vendor_id": "100000001",
  "left_after": "2025-09-01",
  "role": "executive"
}

One object.

• Unknown or unpublished vendor — Vendor not found: "<id>". — pass an id from search_vendors.
• Undated departures — Excluded when left_after is set, and counted in the drop counters.

search_retirements

Executives who will retire or have retired, each with the last day, a confidence and who said so. Editor-confirmed retirements (a published story) come first; after them, people whose own LinkedIn profile says they have retired, marked low confidence. Every row is backed by a sourced claim, and the list grows as retirements are recorded.

Ask it: “Which health-system CEOs have announced they are retiring?”

{
  "status": "announced",
  "seat": "ceo"
}

One object.

• Empty results — No matching retirements are recorded yet — not an error.

search_signals

Recent market signals, newest first. Filter by text, by the entity a signal came from, by type, by source format, or by a detection window.

Ask it: “Show me every funding round in revenue cycle since May.”

{
  "signal_type": "Funding / Investment",
  "detected_after": "2026-05-01",
  "distinct_articles": true,
  "limit": 50
}

An array of signals, newest first.

• Empty array — Nothing matched; there is no coverage note on this tool.

resolve_hospital

Turn a hospital name into the id the relationship lookup accepts. Resolution only, not a profile — it returns ranked candidates so you can pick the right St. Mary’s before you ask about edges.

{
  "query": "Massachusetts General",
  "state": "MA",
  "limit": 5
}

An array of candidates, largest by staffed beds first.

• Empty array — No hospital matched.

get_relationships

Company-to-company edges touching an entity, with provenance: source, evidence quote, evidence tier, a citable article and when it was first seen. The anchor can be a vendor or a hospital, which is what makes “what does this hospital run” answerable.

Ask it: “What technology does Mass General run?”

{
  "entity_id": "100000001",
  "edge_type": "CUSTOMER_OF",
  "limit": 100
}

An array of edges, active first. When some were withheld it is instead { relationships, withheld, note }.

• Unknown id — Entity not found: "<id>". followed by how to pass an id: the id from search_vendors, a numeric slug, or a terminalId. A vendor name is not an id.
• Withheld edges — Counted in withheld: the other organization is unpublished and cannot be named. Say “at least” when counting.

publish_page

Publish a page your assistant composed — a market analysis, a vendor write-up, an article — as a hosted page on clinicalterminal.com, styled like the product and stamped with its publish date. Unlisted by default: only someone with the link can read it. A public page gets a keyword URL, a sitemap listing and a Markdown twin for other agents.

{
  "title": "Texas acute-care hospitals: Q3 news activity",
  "summary": "Twelve Texas systems drove most provider news this quarter.",
  "body_html": "<h1>Texas acute-care activity</h1><p>Baylor Scott and White led signal volume.</p>",
  "page_type": "analysis"
}

One object.

• Rejected HTML — Sending <!doctype>, <html>, <head>, <body>, <style>, <script> or <link>, an inline style or id, an event handler, or an image from an unapproved host is rejected with an error naming each offender. Nothing is silently stripped.
• Too large — body_html over 262,144 bytes. Cut sections rather than truncating.
• Daily quota — 20 publishes per key per UTC day, updates included, shared with publish_comparison.
• Storage quota — 200 live pages per key. Revoking one frees a slot.
• Update of an unknown id — No live page with that artifact_id is published under this account.

publish_comparison

The same mechanics, shape and quota as publish_page, with guidance tuned for a vendor comparison, and page_type defaulting to comparison. A comparison assembled in a chat window dies in the scrollback; this is the version you can send to someone.

{
  "title": "Waystar vs Adonis: denials, 400-bed IDN",
  "summary": "Waystar has broader confirmed hospital traction; Adonis is newer with regional references.",
  "body_html": "<h1>Waystar vs Adonis</h1><p>Waystar leads on confirmed customers.</p>",
  "citations": [
    {
      "label": "Waystar case study",
      "url": "https://www.waystar.com/case-studies/"
    }
  ],
  "source_tools": [
    "get_vendor_dossier",
    "get_relationships"
  ]
}

The same object as publish_page.

• Every publish_page error — Applies here too, against the same shared quota.

list_my_comparisons

Everything published under your key, newest first. This is your exposure audit — the one place to check what of yours is publicly readable.

{
  "limit": 10,
  "include_revoked": false
}

{ ok: true, artifacts }, newest first.

revoke_comparison

Take a published page offline. The body is deleted rather than hidden and the URL stops working within about a minute. Permanent: republishing produces a new URL. Works for pages from either publish tool.

{
  "artifact_id": "waystar-vs-adonis-denials-k3f9x2"
}

{ ok: true, artifact_id }. One stored-page slot is freed.

• Unknown, not yours, or already revoked — The same answer for all three, so ids cannot be probed.

get_brand_kit

The same kit that lives at clinicalterminal.com/pressrelease, returned as data. An assistant that calls it first uses the real marks; one that does not tends to invent a red.

Ask it: “Design a LinkedIn banner in Clinical Terminal's brand”

None — call it with an empty arguments object.

{}

One object.

describe_schema

The column inventory for an allowed dataset, so an assistant can author correct SQL instead of guessing at table shapes.

{
  "dataset": "knowledge_graph",
  "table": "providers"
}

{ dataset, columns }, ordered by table then column position.

• Any failure — Never an error response: columns comes back empty with an error field. An unknown table returns an empty list with no error.

run_analysis_sql

A read-only query for analysis the fixed tools cannot express. One statement, writes rejected, a LIMIT 1000 added when you give none, and capped at 5 GiB scanned.

{
  "sql": "SELECT provider_subtype, COUNT(*) AS n FROM `clinical-ai-design.knowledge_graph.providers` WHERE state = @st GROUP BY 1 ORDER BY n DESC",
  "params": {
    "st": "TX"
  }
}

{ ok, rows, bytesProcessed }.

• Any rejection — Never an error response: ok: false with an error naming the rule — multiple statements, anything but SELECT/WITH, a write keyword anywhere in the text, a dataset or project outside the allowlist, or a scan estimated over 5 GiB.