Skip to main content
Glama

IVFcost.co: US IVF prices, coverage and grants

Mini IVF, natural cycle IVF and INVOcell: posted prices

mini_ivf_cost
Read-onlyIdempotent

What US fertility clinics post on their own pages for mini IVF, minimal or low stimulation IVF, natural cycle IVF and INVOcell, each quoted with its page, whether medications are included and the same clinic's own standard IVF price where it posts one, plus what ASRM (2018) and ESHRE (2025 update) say about who gentler stimulation suits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mini_ivf_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-open-world), and the description adds real substance beyond them: each figure is tied to its source page, flagged for medication inclusion, paired with the clinic's own standard IVF price, and supplemented by named ASRM 2018 and ESHRE 2025 guidance. It still does not say how many clinics are covered or what happens when a clinic posts no price.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One long but well-ordered sentence that leads with the data source and enumerates the per-record fields in sequence. Dense without filler, though a period or two would make it easier to scan.

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?

With no output schema, the description carries the burden of describing return content, and it does so: source page, medication inclusion, standard-IVF comparison and guideline citations. Coverage limits, result counts and behavior for clinics that post no price remain unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate; the baseline applies. The description does useful work by pre-declaring what each returned record contains.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb-resource pair: prices that US fertility clinics 'post on their own pages' for mini IVF, minimal/low stimulation IVF, natural cycle IVF and INVOcell. It scopes the treatment types precisely enough to separate this from standard-IVF cost tools, but it never names a sibling such as estimate_ivf_cost or find_ivf_clinic_prices, so the boundary with those is left implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the treatment-type scope: an agent can infer this is for gentler-stimulation pricing rather than conventional IVF. There is no explicit when-to-use, when-not-to-use, or named alternative for conventional-IVF or doctor-lookup questions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources