Chia Health MCP

Create Checkout

checkout_create

DestructiveIdempotent

Initiate a checkout session for a medication order. Returns checkout details including line items, total, and payment options.

TWO PAYMENT PATHS are supported:

Stripe ACP (preferred): If your platform supports Stripe Agentic Commerce Protocol, provision a Shared Payment Token (SPT) and call checkout_complete to pay instantly.
Payment link (fallback): If ACP/SPT is not available, present the returned payment_url to the patient. This is a Stripe-hosted checkout page where the patient can enter their card and pay directly. After sending the link, call checkout_status to poll for payment completion.

Requires authentication.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`order_id`	Yes	Order ID to create checkout for
`bearer_token`	No	Authentication token for the patient session

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.2/5.0

Behavior4/5

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

The description explains what the tool returns (checkout details including line items, total, payment options) and the payment_url behavior, going beyond the annotations. It does not contradict the annotations and adds context about the preferred vs fallback workflows.

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?

The description is well-structured with a clear purpose sentence and two labeled payment paths, making it easy to scan without being overly verbose. Every sentence adds value.

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?

The description covers the initiation purpose, return contents, authentication requirement, and both follow-up paths. With an output schema present, it sufficiently addresses the complexity of the tool.

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 descriptions cover both parameters fully (100%), so the baseline is 3. The description adds that authentication is required, but no additional parameter details beyond the schema.

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 'Initiate a checkout session for a medication order' with a specific verb and resource, and it differentiates from sibling tools by explaining the two payment paths and referring to checkout_complete and checkout_status.

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 explicitly describes the two payment paths (Stripe ACP preferred, payment link fallback) and instructs to call checkout_complete or checkout_status. It also notes the need for authentication, providing clear usage context, though it doesn't explicitly state when not to use this tool.

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

All Chia Health MCP 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

A3.9/5.0

Disambiguation5/5

Every tool targets a distinct resource and action within the telehealth workflow: auth, consent, eligibility, intake, medications, checkout, order, portal, and provider communication. Even the multiple medication tools (list, details, availability, pricing) have clearly separated purposes, and there is no overlap among the 34 tools.

Naming Consistency5/5

All tool names follow a consistent `domain_verb` or `domain_noun` snake_case pattern, prefixed by their domain (auth_, checkout_, consent_, intake_, medications_, order_, portal_, provider_). There are no mixed conventions or vague verbs, making the API predictable and easy to navigate.

Tool Count2/5

With 34 tools, the server exceeds the 25+ threshold for 'too many' and feels fragmented. Many tools could be consolidated (e.g., medication pricing and availability could fold into details, and consent list/status could be combined). While the scope is broad, the count is excessive for a well-scoped MCP server.

Completeness4/5

The tool surface covers the full patient lifecycle from authentication and consent through eligibility, intake, checkout, order management, and post-order portal features. Minor gaps include lack of order cancellation or order listing, and no explicit intake update mechanism, but these are workable and do not block core workflows.

Resources

Need Help?