com.medigami/mcp

Est-ce que com.medigami/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.medigami/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 87 outils

• analyze_glp1_pathways≈ 250 tokens

  Find all access pathways for a GLP-1 drug (Ozempic, Wegovy, Mounjaro, Zepbound) given patient eligibility factors. Ranks pathways by monthly cost, flags prior-authorization rules and step-therapy, and returns the recommended appeal strategy if denial is likely. WHEN TO USE: User specifically asks about GLP-1 drugs (Ozempic, Wegovy, Mounjaro, Zepbound) — coverage, prior-auth strategy, step-therapy alternatives. WHEN NOT: For non-GLP-1 prescriptions (use optimize_prescription).

  Paramètres, retour & exemple (8)

  Paramètres

  • bmi · number · requis
  • state · string · optionnel
  • has_cvd · boolean · optionnel
  • insurer · string · requis
  • medicare · boolean · optionnel
  • has_diabetes · boolean · optionnel
  • current_copay · number · optionnel
  • tried_step_therapy · array · optionnel
    Drug names already tried under step therapy, e.g. ['metformin'].

  Exemple d'appel

  {"name": "analyze_glp1_pathways", "arguments": {"bmi": 1, "insurer": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• appeal_argument_generator≈ 205 tokens

  [Taxonomy VII.120 — baseline response (public data only)] Generate component arguments for an appeal letter: medical-necessity, contract, policy. WHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one. WHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negotiation path on a non-denied bill, use negotiate_bill_script. EXAMPLES: - Argument blocks for CO-50 with UHC: `{"denial_code":"CO-50","insurer":"UnitedHealthcare"}`

  Paramètres, retour & exemple (4)

  Paramètres

  • insurer · string · optionnel
  • cpt_code · string · optionnel
  • icd10_code · string · optionnel
  • denial_code · string · optionnel

  Exemple d'appel

  {"name": "appeal_argument_generator", "arguments": {"insurer": "texte", "cpt_code": "texte", "icd10_code": "texte", "denial_code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• appeal_escalation_path_finder≈ 254 tokens

  [Taxonomy VII.129 — baseline response (public data only)] Find the correct escalation path for a denied claim (internal appeal → external review → DOI). WHEN TO USE: User needs to know the deadlines and agencies for each step of appealing a denial. Pass state (e.g. 'CA') and insurer for state-specific and insurer-specific values. WHEN NOT: Without state/insurer — still works but returns generic federal defaults. Follow up with state for best answer. EXAMPLES: - CA / UnitedHealthcare escalation path: `{"state":"CA","insurer":"UnitedHealthcare"}`

  Paramètres, retour & exemple (2)

  Paramètres

  • state · string · optionnel
    Two-letter US state code. State-specific external-review deadlines and DOI agency URL are returned when we have them (top 16 states).
  • insurer · string · optionnel
    Insurer canonical name, e.g. 'UnitedHealthcare', 'Aetna'. Used to look up payer-specific appeal windows.

  Exemple d'appel

  {"name": "appeal_escalation_path_finder", "arguments": {"state": "texte", "insurer": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• appeal_success_predictor≈ 202 tokens

  [Taxonomy E.25 — delegates to estimate_appeal_success] Given a denial, predict the probability of a successful appeal. Returns probability with 95% CI, sample size, and recommended appeal-strategy tags. WHEN TO USE: User or caller wants a probabilistic estimate (denial likelihood, appeal success, payment delay, etc.) to decide whether to pursue a path. WHEN NOT: For hard facts (dollar amounts, code definitions, deadlines). Predictions carry confidence bands; call out the uncertainty when you relay the number.

  Paramètres, retour & exemple (4)

  Paramètres

  • state · string · optionnel
  • insurer · string · requis
  • cpt_code · string · requis
  • denial_reason · string · requis

  Exemple d'appel

  {"name": "appeal_success_predictor", "arguments": {"insurer": "texte", "cpt_code": "texte", "denial_reason": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• batch_scan_bills≈ 211 tokens

  Scan multiple medical bills in one call. Returns per-bill anomaly lists + total recovery estimate across the batch. Input is a list of {bill_text, provider?, insurer?} items (max 10 per call). Much faster than serial scan_bill_for_errors when handling a bulk upload. WHEN TO USE: User has multiple bills or EOBs to review at once (e.g. a family's bills from one visit, or a year of statements). WHEN NOT: For a single bill (use scan_bill_for_errors).

  Paramètres, retour & exemple (1)

  Paramètres

  • bills · array · requis

  Exemple d'appel

  {"name": "batch_scan_bills", "arguments": {"bills": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• bill_shock_predictor≈ 272 tokens

  [Taxonomy X.179 — baseline response (public data only)] Predict risk that a planned service will trigger an unexpected large bill. WHEN TO USE: User planning a service and wants to know if it will trigger an unexpected-large-bill situation. Pass expected_charge_usd and optionally cpt_code to get Medicare-ratio context. WHEN NOT: For a bill already received — scan_bill_for_errors first. EXAMPLES: - Check shock risk on $5,000 office visit: `{"expected_charge_usd":5000,"cpt_code":"99213"}`

  Paramètres, retour & exemple (3)

  Paramètres

  • cpt_code · string · optionnel
    Optional CPT code; when provided, the response includes the Medicare national rate and charge-to-Medicare ratio.
  • threshold_usd · number · optionnel
    Override the default shock threshold (default = KFF 2024 average individual deductible = $1,735).
  • expected_charge_usd · number · requis
    The expected out-of-pocket charge in USD (no currency symbol).

  Exemple d'appel

  {"name": "bill_shock_predictor", "arguments": {"expected_charge_usd": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• billing_charge_vs_allowed_delta≈ 174 tokens

  [Taxonomy III.51 — baseline response (public data only)] Delta between billed charge and payer-allowed amount for a claim line. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable. WHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimates, use deductible_impact_calculator or coinsurance_simulator.

  Paramètres, retour & exemple (2)

  Paramètres

  • billed_usd · number · requis
  • allowed_usd · number · requis

  Exemple d'appel

  {"name": "billing_charge_vs_allowed_delta", "arguments": {"billed_usd": 1, "allowed_usd": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• bundling_violation_detector≈ 192 tokens

  [Taxonomy C.16 — delegates to scan_bill_for_errors] Detect CPT unbundling (billing components of a procedure separately to inflate the claim). Uses the CMS NCCI edits plus payer-specific bundling rules. WHEN TO USE: Caller is building or validating a claim payload before submission — format, structure, completeness, alignment. WHEN NOT: For an already-submitted and denied claim, use generate_appeal_letter. For market pricing context, use benchmark_payer_rate.

  Paramètres, retour & exemple (3)

  Paramètres

  • dos · string · optionnel
    Date of service, YYYY-MM-DD.
  • payer · string · optionnel
  • cpt_codes · array · requis

  Exemple d'appel

  {"name": "bundling_violation_detector", "arguments": {"cpt_codes": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• cash_price_estimator≈ 166 tokens

  [Taxonomy III.39 — baseline response (public data only)] Estimate a fair cash price for a service in a given region (no-insurance path). WHEN TO USE: Uninsured/self-pay user wants a fair-market cash price for a service. Returns Medicare national as a floor + commercial-multiple band. WHEN NOT: For insurance-covered scenarios (deductible_impact_calculator + coinsurance_simulator). EXAMPLES: - Cash price for office visit: `{"cpt_code":"99213","zip3":"902"}`

  Paramètres, retour & exemple (2)

  Paramètres

  • zip3 · string · optionnel
  • cpt_code · string · requis

  Exemple d'appel

  {"name": "cash_price_estimator", "arguments": {"cpt_code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• cash_vs_insurance_optimizer≈ 178 tokens

  [Taxonomy H.41 — baseline response (public data only)] For a given service + patient plan, determine whether cash-pay + charity-care beats insurance billing. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan. WHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).

  Paramètres, retour & exemple (4)

  Paramètres

  • cpt_code · string · requis
  • cash_price · number · optionnel
  • deductible_remaining · number · optionnel
  • insurance_cost_estimate · number · optionnel

  Exemple d'appel

  {"name": "cash_vs_insurance_optimizer", "arguments": {"cpt_code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• claim_consistency_checker≈ 177 tokens

  [Taxonomy C.14 — delegates to scan_bill_for_errors] Detect internal contradictions in a claim: time mismatches, mutually exclusive codes, missing required fields, patient-gender/procedure mismatches. WHEN TO USE: Caller is building or validating a claim payload before submission — format, structure, completeness, alignment. WHEN NOT: For an already-submitted and denied claim, use generate_appeal_letter. For market pricing context, use benchmark_payer_rate.

  Paramètres, retour & exemple (1)

  Paramètres

  • claim_payload · object · requis
    Structured claim (CPT + ICD + dates + amounts).

  Exemple d'appel

  {"name": "claim_consistency_checker", "arguments": {"claim_payload": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• claim_duplicate_line_detector≈ 135 tokens

  [Taxonomy IV.75 — baseline response (public data only)] Detect duplicated service lines within a single claim. WHEN TO USE: Caller is building or validating a claim payload before submission — format, structure, completeness, alignment. WHEN NOT: For an already-submitted and denied claim, use generate_appeal_letter. For market pricing context, use benchmark_payer_rate.

  Paramètres, retour & exemple (1)

  Paramètres

  • claim · object · requis

  Exemple d'appel

  {"name": "claim_duplicate_line_detector", "arguments": {"claim": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• claim_rebuttal_generator≈ 145 tokens

  [Taxonomy VII.128 — baseline response (public data only)] Generate a rebuttal to a payer's denial rationale point-by-point. WHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one. WHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negotiation path on a non-denied bill, use negotiate_bill_script.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "claim_rebuttal_generator", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• claim_reconsideration_builder≈ 149 tokens

  [Taxonomy VII.132 — baseline response (public data only)] Build a claim reconsideration request (lighter-weight than a formal appeal). WHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one. WHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negotiation path on a non-denied bill, use negotiate_bill_script.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "claim_reconsideration_builder", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• code_bundle_validator≈ 173 tokens

  [Taxonomy II.25 — baseline response (public data only)] Check a set of CPT codes against NCCI bundling rules (distinct from modifier-based unbundling). WHEN TO USE: User asks about medical codes: what a CPT/ICD/HCPCS code means, whether a code combination is valid, or how to map between them. WHEN NOT: For full bill scans (use scan_bill_for_errors). For appealing a coding-related denial (use generate_appeal_letter).

  Paramètres, retour & exemple (1)

  Paramètres

  • cpt_codes · array · requis
    Array of CPT codes to check for NCCI bundling violations.

  Exemple d'appel

  {"name": "code_bundle_validator", "arguments": {"cpt_codes": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• code_conflict_detector≈ 218 tokens

  [Taxonomy A.5 — delegates to scan_bill_for_errors] Detect CPT unbundling, mutually exclusive code pairs, and NCCI edit violations in a set of codes. Implemented by the bill scanner's anomaly engine. WHEN TO USE: User asks about medical codes: what a CPT/ICD/HCPCS code means, whether a code combination is valid, or how to map between them. WHEN NOT: For full bill scans (use scan_bill_for_errors). For appealing a coding-related denial (use generate_appeal_letter).

  Paramètres, retour & exemple (2)

  Paramètres

  • cpt_codes · array · requis
    Array of CPT codes to check for conflicts.
  • icd10_codes · array · optionnel
    Optional diagnosis codes for medical-necessity conflict checks.

  Exemple d'appel

  {"name": "code_conflict_detector", "arguments": {"cpt_codes": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• coinsurance_simulator≈ 186 tokens

  [Taxonomy III.49 — baseline response (public data only)] Simulate member coinsurance exposure across plan-design variants. WHEN TO USE: User wants to model their coinsurance share of a post-deductible charge. Pass charge_usd and optionally coinsurance_rate. WHEN NOT: For flat-copay services (copay_model). EXAMPLES: - Simulate 20% coinsurance on $1K: `{"charge_usd":1000,"coinsurance_rate":0.2}`

  Paramètres, retour & exemple (2)

  Paramètres

  • charge_usd · number · requis
  • coinsurance_rate · number · optionnel
    Coinsurance rate as a decimal (e.g. 0.20 for 20%). Default is KFF 2024 avg (18%).

  Exemple d'appel

  {"name": "coinsurance_simulator", "arguments": {"charge_usd": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• copay_model≈ 166 tokens

  [Taxonomy III.50 — baseline response (public data only)] Model member copay for a service by plan-design class. WHEN TO USE: User wants the typical copay for a service type (primary / specialist / er). Uses KFF EHBS 2024 averages. WHEN NOT: For patient-specific plan details — copay varies by plan design. EXAMPLES: - Typical specialist copay: `{"service_type":"specialist"}`

  Paramètres, retour & exemple (1)

  Paramètres

  • service_type · string · optionnel · primary | specialist | er | emergency
    Service category. Returns KFF EHBS 2024 average copay for that category.

  Exemple d'appel

  {"name": "copay_model", "arguments": {"service_type": "primary"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• cpt_to_icd_mapper≈ 174 tokens

  [Taxonomy II.21 — baseline response (public data only)] For a given CPT, surface the ICD-10 codes typically paired with it for medical-necessity support. WHEN TO USE: User has a CPT code and wants to know what ICD-10 diagnoses commonly pair with it for medical-necessity support. WHEN NOT: For specific payer policy lookups (code_validation). EXAMPLES: - Common ICDs for 99213: `{"cpt_code":"99213"}`

  Paramètres, retour & exemple (1)

  Paramètres

  • cpt_code · string · requis
    Single CPT/HCPCS code, e.g. '99213'. Returns common ICD-10 pairings from the public co-occurrence table.

  Exemple d'appel

  {"name": "cpt_to_icd_mapper", "arguments": {"cpt_code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• decode_denial≈ 186 tokens

  Decode a CARC (Claim Adjustment Reason Code) denial code into plain English. Returns meaning, category, whether it's typically reversible on appeal, and appeal guidance. Source: public X12 External Code List + CMS/ERISA public rules. Free, no auth. WHEN TO USE: Reference lookups: individual code details, verifying a provider registry entry, checking a prior Medigami response's signature, or tracking an outcome. WHEN NOT: For composite workflows use the higher-level tool that calls these internally.

  Paramètres, retour & exemple (1)

  Paramètres

  • carc_code · string · requis
    CARC/RARC code, e.g. 'CO-16', '16', 'CO-50'.

  Exemple d'appel

  {"name": "decode_denial", "arguments": {"carc_code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• deductible_impact_calculator≈ 176 tokens

  [Taxonomy III.48 — baseline response (public data only)] Estimate how a planned service will draw against the member's deductible. WHEN TO USE: User wants to know how a specific charge affects their deductible (how much draws down, remaining after, post-deductible exposure). WHEN NOT: For total annual out-of-pocket across a year (healthcare_budget_forecaster). EXAMPLES: - Compute deductible drawdown for $4K charge: `{"charge_usd":4000,"deductible_remaining_usd":1735}`

  Paramètres, retour & exemple (2)

  Paramètres

  • charge_usd · number · requis
  • deductible_remaining_usd · number · optionnel

  Exemple d'appel

  {"name": "deductible_impact_calculator", "arguments": {"charge_usd": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• denial_code_explainer≈ 246 tokens

  [Taxonomy VII.131 — baseline response (public data only)] Explain a CARC/RARC denial code in plain language with common causes. WHEN TO USE: User asks 'what does CO-16 mean' or similar — any CARC/RARC code. Returns full X12 table entry when available with meaning, category, typical root cause, primary remediation, and reversibility flag. WHEN NOT: For drafting an appeal (generate_appeal_letter). For the full escalation path (appeal_escalation_path_finder). EXAMPLES: - Explain CARC CO-16: `{"code":"CO-16"}` - Explain CARC CO-50 (medical necessity): `{"code":"CO-50"}`

  Paramètres, retour & exemple (1)

  Paramètres

  • code · string · requis
    CARC/RARC denial code only, e.g. 'CO-16', 'CO-50', 'PR-1'. The tool looks up the code in the public X12 table. Passing the full expanded reason is tolerated (prefix extracted automatically) but the short code is preferred.

  Exemple d'appel

  {"name": "denial_code_explainer", "arguments": {"code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• denial_reason_classifier≈ 150 tokens

  [Taxonomy VI.106 — baseline response (public data only)] Classify a denial letter or remittance advice into normalized denial-reason categories. WHEN TO USE: User or caller wants a probabilistic estimate (denial likelihood, appeal success, payment delay, etc.) to decide whether to pursue a path. WHEN NOT: For hard facts (dollar amounts, code definitions, deadlines). Predictions carry confidence bands; call out the uncertainty when you relay the number.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "denial_reason_classifier", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• denial_response_builder≈ 219 tokens

  [Taxonomy VII.121 — baseline response (public data only)] Build a denial-response package tailored to the denial reason code. WHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one. WHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negotiation path on a non-denied bill, use negotiate_bill_script. EXAMPLES: - Build response package for CO-197: `{"denial_reason":"CO-197","insurer":"Aetna","cpt_code":"45378","amount":1850}`

  Paramètres, retour & exemple (4)

  Paramètres

  • amount · number · optionnel
  • insurer · string · optionnel
  • cpt_code · string · optionnel
  • denial_reason · string · optionnel
    CARC denial code, e.g. 'CO-16'.

  Exemple d'appel

  {"name": "denial_response_builder", "arguments": {"amount": 1, "insurer": "texte", "cpt_code": "texte", "denial_reason": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• dispute_case_builder≈ 150 tokens

  [Taxonomy VII.123 — baseline response (public data only)] Assemble a complete dispute case file including claim, denial, evidence, and timeline. WHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one. WHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negotiation path on a non-denied bill, use negotiate_bill_script.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "dispute_case_builder", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• estimate_appeal_success≈ 326 tokens

  Probability an appeal will be approved, derived from outcome-labeled data weighted by label provenance (IRO determinations, EOB reversals, physician confirmations). Returns probability + 95% CI + sample_size + expected_days_to_resolution + tracking_id. Report the actual outcome later via POST /api/outcomes/record with the same tracking_id to improve future estimates. WHEN TO USE: User or caller wants probability-of-reversal before spending time on an appeal. Returns probability + confidence interval. WHEN NOT: For picking among multiple appeal strategies (appeal_strategy_success_model). As a stand-alone — usually chain into generate_appeal_letter. EXAMPLES: - Gauge CO-50 appeal odds on Aetna: `{"insurer":"Aetna","denial_reason":"CO-50","cpt_code":"72148","state":"TX","amount":1200}`

  Paramètres, retour & exemple (6)

  Paramètres

  • state · string · optionnel
  • amount · number · optionnel
  • insurer · string · requis
  • cpt_code · string · requis
  • diagnosis · string · optionnel
  • denial_reason · string · requis
    medical_necessity | prior_auth | out_of_network | experimental | coding_error

  Exemple d'appel

  {"name": "estimate_appeal_success", "arguments": {"insurer": "texte", "cpt_code": "texte", "denial_reason": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• evidence_pack_generator≈ 151 tokens

  [Taxonomy VII.124 — baseline response (public data only)] Generate an evidence package supporting a claim or appeal (references, studies, policies). WHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one. WHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negotiation path on a non-denied bill, use negotiate_bill_script.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "evidence_pack_generator", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• explain_appeal_success≈ 231 tokens

  Human-readable rationale for an appeal probability. Returns {probability, tier, recommended_posture, rationale, expected_days_to_resolution, tracking_id} grounded in aggregate outcome rates — not model feature weights. Use this when the caller wants 'why' in plain English alongside the number. WHEN TO USE: Reference lookups: individual code details, verifying a provider registry entry, checking a prior Medigami response's signature, or tracking an outcome. WHEN NOT: For composite workflows use the higher-level tool that calls these internally.

  Paramètres, retour & exemple (6)

  Paramètres

  • state · string · optionnel
  • amount · number · optionnel
  • insurer · string · requis
  • cpt_code · string · requis
  • diagnosis · string · optionnel
  • denial_reason · string · requis

  Exemple d'appel

  {"name": "explain_appeal_success", "arguments": {"insurer": "texte", "cpt_code": "texte", "denial_reason": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• fair_price_estimator≈ 215 tokens

  [Taxonomy B.8 — delegates to benchmark_payer_rate] Fair-market price distribution for a service: DP-noised percentiles (p10, p25, p50, p75, p90) for the given CPT in a ZIP3 region. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable. WHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimates, use deductible_impact_calculator or coinsurance_simulator.

  Paramètres, retour & exemple (3)

  Paramètres

  • zip3 · string · requis
    First 3 digits of ZIP.
  • insurer · string · optionnel
    Optional insurer for payer-specific distribution.
  • cpt_code · string · requis

  Exemple d'appel

  {"name": "fair_price_estimator", "arguments": {"zip3": "texte", "cpt_code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• financial_assistance_finder≈ 250 tokens

  [Taxonomy X.181 — baseline response (public data only)] Find applicable financial-assistance programs (hospital charity, 340B, state, pharma). WHEN TO USE: User needs help paying a medical bill. Pass household_income_usd and family_size for FPL-based eligibility flags across 6 programs (501(r) charity, Medicaid, PE, manufacturer PAPs, 340B, state pools). WHEN NOT: For insured users with low exposure (use coinsurance_simulator or deductible_impact_calculator). EXAMPLES: - Find assistance for family of 3 at $45K income: `{"household_income_usd":45000,"family_size":3}`

  Paramètres, retour & exemple (2)

  Paramètres

  • family_size · integer · optionnel
    Number of people in the household. Used to compute FPL threshold.
  • household_income_usd · number · optionnel
    Annual household income in USD. When provided, tool computes FPL ratio and flags likely-eligible programs.

  Exemple d'appel

  {"name": "financial_assistance_finder", "arguments": {"family_size": 1, "household_income_usd": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• financial_exposure_model≈ 134 tokens

  [Taxonomy X.176 — delegates to financial_risk_exposure_model] Model a member's financial exposure. Alias of financial_risk_exposure_model. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan. WHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "financial_exposure_model", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• financial_risk_exposure_model≈ 190 tokens

  [Taxonomy H.42 — baseline response (public data only)] Quantify a patient's financial exposure to medical-debt risk given current plan, health status, and historical claim volatility. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan. WHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).

  Paramètres, retour & exemple (4)

  Paramètres

  • plan_id · string · requis
  • household_income · number · optionnel
  • emergency_savings · number · optionnel
  • chronic_conditions · array · optionnel

  Exemple d'appel

  {"name": "financial_risk_exposure_model", "arguments": {"plan_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• format_citation≈ 363 tokens

  Format an LLM-citable reference to a previously-attested Medigami MCP response. Input: either the full signed envelope that an earlier attested tool returned, OR just a tracking_id. Returns a short citation string, a public verification URL a third party can open to inspect and cryptographically verify the payload, and a long-form attribution block. Use this after any substantive Medigami tool call (scan, estimate, resolve, benchmark) so the user has a verifiable reference to the specific answer and its expiration date. WHEN TO USE: After a substantive tool call, generate a citable string + short URL the LLM can paste into its user-facing response for later verification. WHEN NOT: For non-substantive lookups where citation is unnecessary. EXAMPLES: - Generate a citable URL from a tracking_id: `{"tracking_id":"evt_abc123"}`

  Paramètres, retour & exemple (3)

  Paramètres

  • format · string · optionnel · short | long | both
    short = one-line citation string; long = paragraph attribution; both = return both (default).
  • envelope · object · optionnel
    Full signed envelope returned by an attested Medigami tool (preferred).
  • tracking_id · string · optionnel
    tracking_id alone; the resulting URL will still render but the third party must paste the envelope into the verifier form.

  Exemple d'appel

  {"name": "format_citation", "arguments": {"format": "short", "envelope": {}, "tracking_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• format_medigami_citation≈ 253 tokens

  DEPRECATED ALIAS of format_citation — kept for backward compatibility with v0.1.7 clients. New code should call format_citation directly. WHEN TO USE: Reference lookups: individual code details, verifying a provider registry entry, checking a prior Medigami response's signature, or tracking an outcome. WHEN NOT: For composite workflows use the higher-level tool that calls these internally.

  Paramètres, retour & exemple (3)

  Paramètres

  • format · string · optionnel · short | long | both
    short = one-line citation string; long = paragraph attribution; both = return both (default).
  • envelope · object · optionnel
    Full signed envelope returned by an attested Medigami tool (preferred).
  • tracking_id · string · optionnel
    tracking_id alone; the resulting URL will still render but the third party must paste the envelope into the verifier form.

  Exemple d'appel

  {"name": "format_medigami_citation", "arguments": {"format": "short", "envelope": {}, "tracking_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• generate_appeal_letter≈ 464 tokens

  Generate a legally-grounded insurance appeal letter for a denied claim. Returns the letter as a template with [PATIENT NAME] and [PROVIDER NAME] placeholders (structured-only PHI posture). Includes legal citations, recommended attachments, and appeal-deadline calendar. WHEN TO USE: User has a specific claim denied and wants a drafted appeal letter. Requires insurer, denial_reason (CARC code), cpt_code, diagnosis (ICD-10), and dollar amount. Returns an attested letter with reversal rate, insurer-specific tips, recommended attachments. WHEN NOT: If the user only wants to understand a denial code, use denial_code_explainer first. If they haven't received a formal denial yet, don't draft — clarify status first. For non-CARC disputes (e.g. billing errors pre-adjudication), use scan_bill_for_errors. EXAMPLES: - Draft CO-16 appeal to UHC for office visit: `{"insurer":"UnitedHealthcare","d...

  Paramètres, retour & exemple (6)

  Paramètres

  • state · string · optionnel
    Two-letter US state code for state-specific disclaimers.
  • amount · number · requis
    Dollar amount in dispute (number, no currency symbol).
  • insurer · string · requis
    Insurer canonical name, e.g. 'UnitedHealthcare', 'Aetna'.
  • cpt_code · string · requis
    Single CPT/HCPCS code, e.g. '99213' or 'J0585'.
  • diagnosis · string · requis
    Single ICD-10 code, e.g. 'I10' or 'E11.9'.
  • denial_reason · string · requis
    CARC/RARC denial code, e.g. 'CO-16' or 'CO-97'. Code only — do NOT include the human-readable expansion of the code.

  Exemple d'appel

  {"name": "generate_appeal_letter", "arguments": {"amount": 1, "insurer": "texte", "cpt_code": "texte", "diagnosis": "texte", "denial_reason": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• generate_appeal_letter_v2≈ 224 tokens

  [Taxonomy F.28 — delegates to generate_appeal_letter] [Taxonomy alias] Generate a state-specific insurance appeal letter with UPL-safe disclaimers for 19 US states. Same impl as generate_appeal_letter. WHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one. WHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negotiation path on a non-denied bill, use negotiate_bill_script.

  Paramètres, retour & exemple (6)

  Paramètres

  • state · string · optionnel
  • amount · number · requis
  • insurer · string · requis
  • cpt_code · string · requis
  • diagnosis · string · requis
  • denial_reason · string · requis

  Exemple d'appel

  {"name": "generate_appeal_letter_v2", "arguments": {"amount": 1, "insurer": "texte", "cpt_code": "texte", "diagnosis": "texte", "denial_reason": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_appeal_deadline≈ 234 tokens

  External-review filing deadline for a state + the date of the FINAL adverse determination. Returns the deadline date, the statutory window label + citation, and whether the exact state-specific window still needs verification (most states carry a conservative NAIC-model 4-month floor unless statute-confirmed, e.g. CA/NY). Free, no auth. WHEN TO USE: Reference lookups: individual code details, verifying a provider registry entry, checking a prior Medigami response's signature, or tracking an outcome. WHEN NOT: For composite workflows use the higher-level tool that calls these internally.

  Paramètres, retour & exemple (2)

  Paramètres

  • state · string · optionnel
    2-letter US state
  • denial_date · string · requis
    ISO date (YYYY-MM-DD) of the FINAL adverse determination

  Exemple d'appel

  {"name": "get_appeal_deadline", "arguments": {"denial_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_venue≈ 153 tokens

  Where and how to file an external review for a given state — the venue name, filing channel (portal/mail/fax), portal URL, and whether expedited review is available. Free, no auth. WHEN TO USE: Reference lookups: individual code details, verifying a provider registry entry, checking a prior Medigami response's signature, or tracking an outcome. WHEN NOT: For composite workflows use the higher-level tool that calls these internally.

  Paramètres, retour & exemple (1)

  Paramètres

  • state · string · optionnel
    2-letter US state

  Exemple d'appel

  {"name": "get_venue", "arguments": {"state": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• healthcare_budget_forecaster≈ 137 tokens

  [Taxonomy X.183 — baseline response (public data only)] Forecast a household's annual healthcare spend based on plan + utilization. WHEN TO USE: User planning annual healthcare spend, comparing plans, or estimating worst-case exposure. WHEN NOT: For a specific procedure cost (benchmark_payer_rate). EXAMPLES: - Forecast annual spend range: `{}`

  Paramètres, retour & exemple (2)

  Paramètres

  • plan_oop_max_usd · number · optionnel
  • plan_deductible_usd · number · optionnel

  Exemple d'appel

  {"name": "healthcare_budget_forecaster", "arguments": {"plan_oop_max_usd": 1, "plan_deductible_usd": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• icd_to_cpt_mapper≈ 164 tokens

  [Taxonomy II.22 — baseline response (public data only)] For a given ICD-10, surface the CPT codes typically billed for that diagnosis. WHEN TO USE: User has an ICD-10 diagnosis and wants to know what CPTs are commonly billed for it. WHEN NOT: For planning specific services (use benchmark_payer_rate once the CPT is chosen). EXAMPLES: - Common CPTs for essential hypertension: `{"icd10_code":"I10"}`

  Paramètres, retour & exemple (1)

  Paramètres

  • icd10_code · string · requis
    Single ICD-10-CM code, e.g. 'I10'. Returns common CPT candidates.

  Exemple d'appel

  {"name": "icd_to_cpt_mapper", "arguments": {"icd10_code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• inflation_adjusted_price_model≈ 161 tokens

  [Taxonomy III.46 — baseline response (public data only)] Inflation-adjusted price comparison across years for a CPT. WHEN TO USE: User has a historical dollar amount and wants it adjusted for medical-care inflation to a given year. WHEN NOT: For current market prices (benchmark_payer_rate). EXAMPLES: - Adjust $1K 3yr forward at medical CPI: `{"base_amount_usd":1000,"years":3}`

  Paramètres, retour & exemple (2)

  Paramètres

  • years · number · requis
  • base_amount_usd · number · requis

  Exemple d'appel

  {"name": "inflation_adjusted_price_model", "arguments": {"years": 1, "base_amount_usd": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• insurance_plan_optimizer≈ 201 tokens

  [Taxonomy H.39 — baseline response (public data only)] Given a patient's historical claim patterns, rank available insurance plans by expected annual cost. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan. WHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).

  Paramètres, retour & exemple (5)

  Paramètres

  • zip_code · string · requis
  • income_band · string · optionnel
  • household_size · integer · optionnel
  • historical_spend · number · optionnel
    Prior-year OOP spend.
  • chronic_conditions · array · optionnel

  Exemple d'appel

  {"name": "insurance_plan_optimizer", "arguments": {"zip_code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• insurance_response_interpreter≈ 211 tokens

  [Taxonomy F.31 — baseline response (public data only)] Parse an insurer's response letter or EOB into structured fields: denial reason codes, appeal rights, deadlines, next-step recommendations. WHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one. WHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negotiation path on a non-denied bill, use negotiate_bill_script.

  Paramètres, retour & exemple (2)

  Paramètres

  • response_text · string · requis
    Insurer response or EOB text.
  • response_type · string · optionnel · denial | partial_denial | eob | appeal_response

  Exemple d'appel

  {"name": "insurance_response_interpreter", "arguments": {"response_text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• insurance_value_optimizer≈ 134 tokens

  [Taxonomy X.185 — baseline response (public data only)] Recommend insurance-plan selections to maximize value given projected utilization. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan. WHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "insurance_value_optimizer", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lookup_cpt≈ 246 tokens

  Look up a CPT or HCPCS-J code or search by keyword. Covers the most common outpatient billing codes (E/M, preventive, lab, imaging, procedure, cardiology, therapy, behavioral, vaccine, injectable drugs). Note: CPT is a registered trademark of the American Medical Association; full-dataset commercial use requires an AMA license. This tool provides short descriptors for identification in billing-review workflows. WHEN TO USE: User asks about a specific CPT/HCPCS procedure code or wants to search for codes by procedure description. WHEN NOT: For the expected ICD pairings (icd_to_cpt_mapper or cpt_to_icd_mapper). EXAMPLES: - Find CPT for routine office visit: `{"query":"office visit established patient"}`

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · requis
    CPT / HCPCS-J code ('99213', 'J1885') or keyword ('knee MRI', 'colonoscopy').

  Exemple d'appel

  {"name": "lookup_cpt", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lookup_icd10≈ 228 tokens

  Look up an ICD-10-CM diagnosis code or search by keyword. Input is either an exact code (e.g. 'E11.21') or a free-text description phrase ('type 2 diabetes with nephropathy'). Returns either the matching code + description or up to 20 candidate matches. Use when a clinical note uses non-standard phrasing and the correct code is needed for billing. WHEN TO USE: User asks about a specific ICD-10 diagnosis code or wants RAG-search over ICD-10 for a condition name. WHEN NOT: For the matching CPT codes (cpt_to_icd_mapper). For code validation against a payer (code_validation). EXAMPLES: - Find ICD-10 for hypertension: `{"query":"essential hypertension"}`

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · requis
    ICD-10-CM code (e.g. 'I10', 'E11.21') or keyword search.

  Exemple d'appel

  {"name": "lookup_icd10", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lookup_npi≈ 236 tokens

  Look up a provider in the CMS NPPES National Provider Identifier registry. Accepts a 10-digit NPI number OR a provider name (optionally narrowed by 2-char state). Returns up to 20 matches with entity type, specialty, taxonomy code, address, and status. Source: CMS NPPES public API (free, no key required). WHEN TO USE: User wants to verify a specific provider by NPI number, or find a provider by name + state. WHEN NOT: For provider performance analytics (provider_efficiency_score). EXAMPLES: - Look up a provider by NPI number: `{"npi_number":"1234567893"}`

  Paramètres, retour & exemple (2)

  Paramètres

  • query · string · requis
    10-digit NPI (e.g. '1234567890') or provider name ('Jane Smith').
  • state · string · optionnel
    Optional 2-char state abbreviation to narrow a name search.

  Exemple d'appel

  {"name": "lookup_npi", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lookup_provider_taxonomy≈ 174 tokens

  Look up a NUCC provider taxonomy code (the specialty codes used on HIPAA transactions + NPI registrations) or search by keyword. Returns classification + type + optional specialization. Source: NUCC Health Care Provider Taxonomy Code Set (public; CMS-accepted). WHEN TO USE: Resolving a NUCC provider taxonomy code to its specialty description. WHEN NOT: For finding a provider by specialty in a region (not yet implemented).

  Paramètres, retour & exemple (1)

  Paramètres

  • query · string · requis
    Taxonomy code ('207Q00000X') or keyword ('cardiology', 'pediatrics').

  Exemple d'appel

  {"name": "lookup_provider_taxonomy", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• market_price_distribution_model≈ 152 tokens

  [Taxonomy III.55 — baseline response (public data only)] Full DP-noised market price distribution for a CPT+region pair. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable. WHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimates, use deductible_impact_calculator or coinsurance_simulator.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "market_price_distribution_model", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• maximize_recovery≈ 128 tokens

  Given a prior scan_id, returns a prioritized action list: anomalies ranked by (expected overcharge x recovery probability), with the next steps to pursue each. Use after scan_bill_for_errors. WHEN TO USE: User has already run scan_bill_for_errors and wants the anomalies ranked by expected dollar recovery. WHEN NOT: As a first call — always scan first.

  Paramètres, retour & exemple (1)

  Paramètres

  • scan_id · string · requis

  Exemple d'appel

  {"name": "maximize_recovery", "arguments": {"scan_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• medical_spending_analyzer≈ 136 tokens

  [Taxonomy X.184 — baseline response (public data only)] Analyze a patient's medical spending over a period and surface optimization opportunities. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan. WHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "medical_spending_analyzer", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• medigami_deadline≈ 370 tokens

  Federal appeal-deadline window (ERISA §503 internal-appeal / ACA §2719 external-review / NSA IDR) for a plan type. Public regulator data, k-anonymity floored, not legal advice. WHEN TO USE: Reference lookups: individual code details, verifying a provider registry entry, checking a prior Medigami response's signature, or tracking an outcome. WHEN NOT: For composite workflows use the higher-level tool that calls these internally.

  Paramètres, retour & exemple (2)

  Paramètres

  • state · string · requis
    2-letter US state (echoed on the row; the deadline window itself is federal, not state-varying).
  • plan_type · string · requis
    e.g. 'self_funded', 'aca_marketplace', 'medicare', 'medicaid'.

  Exemple d'appel

  {"name": "medigami_deadline", "arguments": {"state": "texte", "plan_type": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cta": {}, "rows": [], "as_of": "texte", "basis": "texte", "command": "texte", "refused": "texte", "permalink": "texte", "source_url": "texte", "unresolved": [], "result_kind": "texte"}}

• medigami_odds≈ 371 tokens

  Historical external-review overturn rate published by the state regulator for the insurer you name, in a regulated venue (CA/NY/MD/NJ/MI/OH/NC). Returns one insurer's own rate — not a comparison or ranking against other insurers. Public regulator data, k-anonymity floored, not legal advice. WHEN TO USE: Reference lookups: individual code details, verifying a provider registry entry, checking a prior Medigami response's signature, or tracking an outcome. WHEN NOT: For composite workflows use the higher-level tool that calls these internally.

  Paramètres, retour & exemple (2)

  Paramètres

  • state · string · requis
    Venue state, e.g. 'CA', 'NY'.
  • insurer · string · requis
    Insurer / payer name.

  Exemple d'appel

  {"name": "medigami_odds", "arguments": {"state": "texte", "insurer": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cta": {}, "rows": [], "as_of": "texte", "basis": "texte", "command": "texte", "refused": "texte", "permalink": "texte", "source_url": "texte", "unresolved": [], "result_kind": "texte"}}

• medigami_rate≈ 342 tokens

  A hospital's own MRF-published negotiated rate for a CPT code (no billed-amount comparison — use medigami_roast for that). Public regulator data, k-anonymity floored, not legal advice. WHEN TO USE: Reference lookups: individual code details, verifying a provider registry entry, checking a prior Medigami response's signature, or tracking an outcome. WHEN NOT: For composite workflows use the higher-level tool that calls these internally.

  Paramètres, retour & exemple (2)

  Paramètres

  • cpt · string · requis
    CPT/HCPCS procedure code.
  • hospital · string · requis
    Hospital / facility name.

  Exemple d'appel

  {"name": "medigami_rate", "arguments": {"cpt": "texte", "hospital": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cta": {}, "rows": [], "as_of": "texte", "basis": "texte", "command": "texte", "refused": "texte", "permalink": "texte", "source_url": "texte", "unresolved": [], "result_kind": "texte"}}

• medigami_roast≈ 368 tokens

  Compare a billed charge against a hospital's own MRF-published negotiated rate for a CPT code; returns the markup multiple. Public regulator data, k-anonymity floored, not legal advice. WHEN TO USE: Reference lookups: individual code details, verifying a provider registry entry, checking a prior Medigami response's signature, or tracking an outcome. WHEN NOT: For composite workflows use the higher-level tool that calls these internally.

  Paramètres, retour & exemple (3)

  Paramètres

  • cpt · string · requis
    CPT/HCPCS procedure code.
  • hospital · string · requis
    Hospital / facility name.
  • billed_amount · number · requis
    Amount billed, USD.

  Exemple d'appel

  {"name": "medigami_roast", "arguments": {"cpt": "texte", "hospital": "texte", "billed_amount": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"cta": {}, "rows": [], "as_of": "texte", "basis": "texte", "command": "texte", "refused": "texte", "permalink": "texte", "source_url": "texte", "unresolved": [], "result_kind": "texte"}}

• negotiate_bill_script≈ 338 tokens

  Generate a phone script the user can read when negotiating a medical bill directly with the provider. Combines DP-noised commercial rate benchmarks + the caller's household income + federal charity-care rules (IRS §501(r)) into three negotiation angles: financial assistance, self-pay discount, and itemized-bill coding review. Returns the script + reference-only benchmark range (for the user's own research, not an insurance-consulting recommendation) + charity-care tier. Output is educational only; the user negotiates on their own behalf. Some states (notably NY, FL, CA) regulate public-adjuster activity — the attached disclaimer references this. WHEN TO USE: User wants talking points and a target settlement range to negotiate a medical bill with the provider. Best for self-pay and out-of-network balances. WHEN NOT: For a bill that was denied (generate_appeal_letter — the payer, not ...

  Paramètres, retour & exemple (7)

  Paramètres

  • zip3 · string · optionnel
  • state · string · optionnel
  • insurer · string · optionnel
  • cpt_code · string · requis
  • billed_amount · number · requis
  • household_size · integer · optionnel
  • household_income_annual · number · optionnel

  Exemple d'appel

  {"name": "negotiate_bill_script", "arguments": {"cpt_code": "texte", "billed_amount": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• negotiation_strategy_generator≈ 218 tokens

  [Taxonomy F.30 — baseline response (public data only)] Given a bill + patient situation, generate a ranked negotiation strategy: hardship appeal, charity-care application, itemization request, phone scripts. WHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one. WHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negotiation path on a non-denied bill, use negotiate_bill_script.

  Paramètres, retour & exemple (4)

  Paramètres

  • provider · string · optionnel
  • situation · string · optionnel · uninsured | underinsured | hardship | dispute
  • bill_amount · number · requis
  • insurance_status · string · optionnel

  Exemple d'appel

  {"name": "negotiation_strategy_generator", "arguments": {"bill_amount": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• optimize_prescription≈ 255 tokens

  Find the lowest-cost path for a prescription: generics, biosimilars, GoodRx coupons, manufacturer assistance, 90-day fills, and mail-order vs retail comparison. Returns ranked options with annual savings vs current copay. WHEN TO USE: User asks about prescription cost — lowest-price generic, biosimilar, GoodRx coupon, mail-order, manufacturer assistance, or 90-day fill options. WHEN NOT: For insurance-covered Rx copay questions (use copay_model). For medical necessity appeals of formulary denials (use generate_appeal_letter). EXAMPLES: - Find cheapest path for atorvastatin 20mg: `{"drug_name":"atorvastatin 20mg","current_insurance_cost_30day":45,"is_maintenance_med":true}`

  Paramètres, retour & exemple (5)

  Paramètres

  • ndc_code · string · optionnel
  • zip_code · string · optionnel
  • drug_name · string · requis
  • is_maintenance_med · boolean · optionnel
  • current_insurance_cost_30day · number · optionnel

  Exemple d'appel

  {"name": "optimize_prescription", "arguments": {"drug_name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• out_of_pocket_optimizer≈ 130 tokens

  [Taxonomy X.174 — baseline response (public data only)] Optimize out-of-pocket spend across a sequence of planned services. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan. WHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "out_of_pocket_optimizer", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• overpriced_service_detector≈ 152 tokens

  [Taxonomy III.53 — baseline response (public data only)] Flag services billed materially above market percentile thresholds. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable. WHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimates, use deductible_impact_calculator or coinsurance_simulator.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "overpriced_service_detector", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• patient_cost_explainer≈ 130 tokens

  [Taxonomy X.182 — baseline response (public data only)] Explain why a specific charge appears on a bill in plain language. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan. WHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "patient_cost_explainer", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• patient_cost_forecaster≈ 205 tokens

  [Taxonomy H.38 — baseline response (public data only)] Given a patient's plan + predicted care needs, forecast annual out-of-pocket spend across expected claims. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan. WHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).

  Paramètres, retour & exemple (3)

  Paramètres

  • plan_id · string · requis
  • chronic_conditions · array · optionnel
    ICD-10 codes for chronic care.
  • expected_procedures · array · optionnel
    CPT codes expected this year.

  Exemple d'appel

  {"name": "patient_cost_forecaster", "arguments": {"plan_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• patient_financial_risk_score≈ 132 tokens

  [Taxonomy X.186 — baseline response (public data only)] Score a patient's financial risk exposure from planned or ongoing care. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan. WHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "patient_financial_risk_score", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• payer_specific_appeal_templates≈ 146 tokens

  [Taxonomy VII.130 — baseline response (public data only)] Return payer-specific appeal templates known to perform well. WHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one. WHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negotiation path on a non-denied bill, use negotiate_bill_script.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "payer_specific_appeal_templates", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• payment_plan_optimizer≈ 155 tokens

  [Taxonomy X.180 — baseline response (public data only)] Optimize a payment plan structure for a patient balance. WHEN TO USE: User has a balance and wants to structure a payment plan. Pass balance_usd and months. WHEN NOT: If user may qualify for charity care — run financial_assistance_finder first. EXAMPLES: - 12-month plan for $3K balance: `{"balance_usd":3000,"months":12}`

  Paramètres, retour & exemple (2)

  Paramètres

  • months · integer · optionnel
  • balance_usd · number · requis

  Exemple d'appel

  {"name": "payment_plan_optimizer", "arguments": {"balance_usd": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• price_anomaly_detector≈ 150 tokens

  [Taxonomy III.52 — baseline response (public data only)] Detect service-line prices statistically anomalous versus market. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable. WHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimates, use deductible_impact_calculator or coinsurance_simulator.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "price_anomaly_detector", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• price_outlier_detector≈ 152 tokens

  [Taxonomy III.56 — baseline response (public data only)] Detect claim-line outliers relative to a learned market distribution. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable. WHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimates, use deductible_impact_calculator or coinsurance_simulator.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "price_outlier_detector", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• price_recommendation_engine≈ 159 tokens

  [Taxonomy III.58 — baseline response (public data only)] Recommend a reasonable price to propose to a provider for a service (self-pay or negotiation). WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable. WHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimates, use deductible_impact_calculator or coinsurance_simulator.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "price_recommendation_engine", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• price_variance_analyzer≈ 206 tokens

  [Taxonomy B.9 — baseline response (public data only)] Given a target price and a CPT+region, return how many standard deviations above/below the market the target sits, plus confidence. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable. WHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimates, use deductible_impact_calculator or coinsurance_simulator.

  Paramètres, retour & exemple (3)

  Paramètres

  • zip3 · string · requis
  • cpt_code · string · requis
  • observed_price · number · requis
    Price to evaluate, USD.

  Exemple d'appel

  {"name": "price_variance_analyzer", "arguments": {"zip3": "texte", "cpt_code": "texte", "observed_price": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• procedure_affordability_ranker≈ 130 tokens

  [Taxonomy X.177 — baseline response (public data only)] Rank a set of procedures by affordability for a given member. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan. WHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "procedure_affordability_ranker", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• procedure_cost_decomposition≈ 158 tokens

  [Taxonomy III.57 — baseline response (public data only)] Decompose the cost of a procedure into component services + facility + professional fees. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable. WHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimates, use deductible_impact_calculator or coinsurance_simulator.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "procedure_cost_decomposition", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• regional_price_benchmark≈ 152 tokens

  [Taxonomy III.43 — baseline response (public data only)] Regional price benchmark for a CPT at state/metro/ZIP3 granularity. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable. WHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimates, use deductible_impact_calculator or coinsurance_simulator.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "regional_price_benchmark", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• resolve_codes≈ 269 tokens

  [Taxonomy A.1 — baseline response (public data only)] Unified code resolver — free-form query or clinical description → ranked ICD-10-CM, CPT, and HCPCS codes with confidence scores. Use when you need to translate symptoms, procedures, or diagnoses into billable codes without running three separate lookups. WHEN TO USE: User asks about medical codes: what a CPT/ICD/HCPCS code means, whether a code combination is valid, or how to map between them. WHEN NOT: For full bill scans (use scan_bill_for_errors). For appealing a coding-related denial (use generate_appeal_letter).

  Paramètres, retour & exemple (3)

  Paramètres

  • query · string · requis
    Free-form clinical description, symptom, or procedure.
  • code_types · array · optionnel
    Optional filter — defaults to all three.
  • max_results · integer · optionnel
    Cap on ranked results. Default 5.

  Exemple d'appel

  {"name": "resolve_codes", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• resolve_denial≈ 282 tokens

  End-to-end denial resolution: returns appeal probability + confidence interval + a drafted letter template grounded in aggregate outcome data + plan-context flags (ERISA, restrictive-adjuster state). One call, one tracking_id. No recovery-financing product is offered by this tool. WHEN TO USE: Single-shot composite: user has a specific denial and wants scan + estimate + appeal + citation in one call. WHEN NOT: For nuanced step-by-step workflows, call the individual tools in order. EXAMPLES: - End-to-end CO-197 denial resolution: `{"insurer":"Aetna","denial_reason":"CO-197","cpt_code":"45378","state":"TX","amount":1850}`

  Paramètres, retour & exemple (7)

  Paramètres

  • state · string · optionnel
  • amount · number · optionnel
  • insurer · string · requis
  • cpt_code · string · requis
  • diagnosis · string · optionnel
  • denial_reason · string · requis
  • plan_type_hint · string · optionnel
    self-funded | aca_marketplace | medicare | medicaid | ...

  Exemple d'appel

  {"name": "resolve_denial", "arguments": {"insurer": "texte", "cpt_code": "texte", "denial_reason": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• scan_bill_for_errors≈ 320 tokens

  Scan a medical bill or EOB text for errors: duplicate charges, CPT unbundling, upcoding, facility-fee overcharges. Returns flagged anomalies with estimated dollar impact and a total recovery estimate. PHI WARNING: bill text typically contains PHI (patient name, DOB, MRN, insurer ID). Medigami runs a server-side PHI redactor before any downstream LLM call when scan_bill is invoked from the public SKU, but best practice is to redact client-side before passing the bill through an LLM tool call. For your own bill only — this tool is not for reviewing someone else's claims. WHEN TO USE: User pastes or uploads a medical bill, EOB, itemized statement, hospital charge summary, or similar. The bill text can be raw (OCR output fine) — the scanner parses it. Prefer this over manual line-by-line analysis for any bill above ~$100. WHEN NOT: For a denial appeal (generate_appeal_letter). For pre-...

  Paramètres, retour & exemple (5)

  Paramètres

  • total · number · optionnel
  • insurer · string · optionnel
  • provider · string · optionnel
  • zip_code · string · optionnel
  • bill_text · string · requis
    Bill/EOB text. Client-side redaction recommended.

  Exemple d'appel

  {"name": "scan_bill_for_errors", "arguments": {"bill_text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• settlement_optimizer≈ 217 tokens

  [Taxonomy F.32 — baseline response (public data only)] For a disputed bill, compute the optimal settlement target price balancing probability of acceptance against amount saved. WHEN TO USE: User has a denied claim and wants to appeal, or is preparing arguments / evidence / escalation steps for one. WHEN NOT: For explaining what a denial code means without drafting an appeal, use denial_code_explainer first. For finding a negotiation path on a non-denied bill, use negotiate_bill_script.

  Paramètres, retour & exemple (4)

  Paramètres

  • provider · string · optionnel
  • bill_amount · number · requis
  • dispute_leverage · string · optionnel · high | medium | low
  • patient_ability_to_pay · number · optionnel
    Monthly discretionary income, USD.

  Exemple d'appel

  {"name": "settlement_optimizer", "arguments": {"bill_amount": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• specialty_price_benchmark≈ 151 tokens

  [Taxonomy III.44 — baseline response (public data only)] Price benchmark for a CPT within a specific provider specialty. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable. WHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimates, use deductible_impact_calculator or coinsurance_simulator.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "specialty_price_benchmark", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• submit_denial_letter≈ 429 tokens

  Submit a medical-claim denial letter to the Medigami Denial Common Crawl (public aggregate dataset). Consent-gated — caller must pass consent=true to attest the submission is voluntary. Server-side PHI scrubber runs before any storage; the public aggregate contains only coded fields (insurer_canonical, denial_reason_code, state, cpt_category, dollars_bin, days_to_resolution_bin). Raw text is never republished. Optional tracking_id closes the outcome loop to a prior Medigami scan / resolve call. WHEN TO USE: User wants to contribute a denial letter to the public Denial Common Crawl (consent-gated). PHI is scrubbed before aggregation. WHEN NOT: Just to explain a denial (denial_code_explainer). To draft a response (generate_appeal_letter).

  Paramètres, retour & exemple (8)

  Paramètres

  • state · string · optionnel
    2-char US state code or empty.
  • amount · number · optionnel
  • consent · boolean · requis
    MUST be true — caller attests the submission is voluntary.
  • cpt_code · string · optionnel
  • letter_text · string · requis
    Raw denial-letter text. PHI scrubbed server-side.
  • tracking_id · string · optionnel
    Optional prior Medigami tracking_id to close the outcome loop.
  • outcome_code · string · optionnel
    Optional: member_abandoned | appealed_won | appealed_lost | appealed_partial | pending
  • days_to_resolution · integer · optionnel

  Exemple d'appel

  {"name": "submit_denial_letter", "arguments": {"consent": true, "letter_text": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• supporting_document_selector≈ 200 tokens

  [Taxonomy VII.135 — baseline response (public data only)] Select optimal supporting documents for an appeal from an available document pool. WHEN TO USE: User is preparing an appeal and needs a ranked list of supporting documents for the denial category. Pass denial_code. WHEN NOT: Without denial_code — still returns generic docs but category-specific ranking is the high-value output. EXAMPLES: - Docs for a CO-50 medical-necessity denial: `{"denial_code":"CO-50"}`

  Paramètres, retour & exemple (2)

  Paramètres

  • denial_code · string · optionnel
    CARC denial code, e.g. 'CO-50'. Drives category-specific document ranking.
  • denial_reason · string · optionnel
    Alias for denial_code.

  Exemple d'appel

  {"name": "supporting_document_selector", "arguments": {"denial_code": "texte", "denial_reason": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• treatment_cost_comparator≈ 131 tokens

  [Taxonomy X.178 — baseline response (public data only)] Compare expected costs across treatment alternatives for a condition. WHEN TO USE: User is planning for a medical expense, comparing plan options, looking for financial assistance, or trying to structure a payment plan. WHEN NOT: For billing-error analysis (scan_bill_for_errors) or appeal drafting (generate_appeal_letter).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "treatment_cost_comparator", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• unbundling_detector≈ 133 tokens

  [Taxonomy II.26 — delegates to scan_bill_for_errors] Detect CPT unbundling patterns in a claim. Alias of scan_bill_for_errors. WHEN TO USE: User asks about medical codes: what a CPT/ICD/HCPCS code means, whether a code combination is valid, or how to map between them. WHEN NOT: For full bill scans (use scan_bill_for_errors). For appealing a coding-related denial (use generate_appeal_letter).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "unbundling_detector", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_attestation≈ 327 tokens

  Verify an Ed25519-signed Medigami MCP response envelope — confirm a medical-bill / appeal / denial / rate answer came from Medigami and hasn't been tampered with. Input: the signed envelope + a public key (PEM) or expected-fingerprint you pinned out-of-band. Returns {valid, reason, tracking_id, timestamp, exp, public_key_fingerprint} so callers can cite the result as FRE 902(14) self-authenticating evidence. Usage: (a) Preferred: supply public_key_pem pinned out-of-band. (b) Otherwise: supply expected_fingerprint (SHA-256 of the pinned key); the envelope's embedded fingerprint is compared against it AND the key is fetched over HTTPS from the envelope's public_key_url (or Medigami's well-known URL) for signature verification. Freshness (exp) and fingerprint equality are both checked. Non-repudiation note: this tool deliberately does NOT silently fall back to the local server's ke...

  Paramètres, retour & exemple (3)

  Paramètres

  • envelope · object · requis
    The signed response envelope
  • public_key_pem · string · optionnel
    PEM public key content (preferred)
  • expected_fingerprint · string · optionnel
    SHA-256 hex of the PEM public key you trust

  Exemple d'appel

  {"name": "verify_attestation", "arguments": {"envelope": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_dea_authorization≈ 262 tokens

  Validate the format + checksum of a DEA registration number (format: [A-Z][A-Z9][0-9]{7}; public checksum algorithm). Useful as a sanity check on a DEA number you were given (e.g. on a prescription label or a provider's letterhead). Scope note: this tool confirms the number is well-formed — it does NOT verify current registration status or the specific controlled-substance schedule the holder is authorized to prescribe. Authority verification requires a licensed DEA data broker (DEA ARCOS, RxMix). WHEN TO USE: Checking if a provider's DEA registration covers a specific controlled-substance CPT. WHEN NOT: For non-controlled-substance claims.

  Paramètres, retour & exemple (2)

  Paramètres

  • cpt_code · string · optionnel
    Optional CPT context; tool does not map CPT to controlled-substance schedule.
  • dea_number · string · requis
    9-char DEA registration (e.g. 'AB1234563').

  Exemple d'appel

  {"name": "verify_dea_authorization", "arguments": {"dea_number": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_mcp_response≈ 202 tokens

  DEPRECATED ALIAS of verify_attestation — kept for backward compatibility with v0.1.7 clients. New code should call verify_attestation directly. WHEN TO USE: Reference lookups: individual code details, verifying a provider registry entry, checking a prior Medigami response's signature, or tracking an outcome. WHEN NOT: For composite workflows use the higher-level tool that calls these internally.

  Paramètres, retour & exemple (3)

  Paramètres

  • envelope · object · requis
    The signed response envelope
  • public_key_pem · string · optionnel
    PEM public key content (preferred)
  • expected_fingerprint · string · optionnel
    SHA-256 hex of the PEM public key you trust

  Exemple d'appel

  {"name": "verify_mcp_response", "arguments": {"envelope": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• watch_appeal_outcome≈ 189 tokens

  Subscribe to an appeal outcome by tracking_id. Blocks up to `timeout_seconds` (default 300). Returns the outcome payload as soon as it's recorded, or {status: 'timeout'} if nothing resolved within the window — caller re-invokes to keep watching. Tracking ids are returned by estimate_appeal_success and other Tier 3 moat tools. WHEN TO USE: Caller wants to subscribe to the outcome of an in-flight appeal by tracking_id. WHEN NOT: One-shot queries — prefer the callbacks via /api/outcomes/record.

  Paramètres, retour & exemple (2)

  Paramètres

  • tracking_id · string · requis
  • timeout_seconds · integer · optionnel

  Exemple d'appel

  {"name": "watch_appeal_outcome", "arguments": {"tracking_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• watch_claim_denial≈ 150 tokens

  Subscribe to a claim denial event for a given scan_id. Blocks up to `timeout_seconds`. Returns {status: 'denied', ...} as soon as the payer marks the claim denied in claim_status_history, or {status: 'timeout'} if no denial observed within the window. WHEN TO USE: Caller wants to stream denial events for a set of claims. WHEN NOT: One-shot queries.

  Paramètres, retour & exemple (2)

  Paramètres

  • scan_id · string · requis
  • timeout_seconds · integer · optionnel

  Exemple d'appel

  {"name": "watch_claim_denial", "arguments": {"scan_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• zip_based_price_variance≈ 151 tokens

  [Taxonomy III.41 — baseline response (public data only)] Report price variance for a CPT across ZIP3 regions with DP noise. WHEN TO USE: User wants to understand what a service typically costs, compare prices across regions/providers, or gauge whether a billed amount is reasonable. WHEN NOT: For a specific bill they have in hand, scan_bill_for_errors is more actionable. For insurance-path estimates, use deductible_impact_calculator or coinsurance_simulator.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "zip_based_price_variance", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.medigami.com/public/mcp