Skip to main content
Glama
Sign In

IVFcost.co: US IVF prices, coverage and grants

by co.ivfcost
OverviewDiscussionsAdmin

The doctors US fertility clinics list

fertility_clinic_doctors
Read-onlyIdempotent

The doctors US fertility clinics list on their own websites, by name exactly as the clinic writes it, with the role it gives each, the page and the date it was read. Give a state (optionally a city) for every clinic there that lists its doctors, or a doctor's name to find the clinic whose site lists that doctor. Doctors move between practices: the date says when the clinic's page was read.

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": "fertility_clinic_doctors"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city to narrow the list (for example Phoenix).
stateNoA US state: its two-letter code (TX) or its name (Texas). DC counts as a state here.
doctorNoOptional doctor's name, or part of it (for example Malizia), searched in every state when no state is given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the bar is lower. The description adds genuinely useful context the annotations cannot: the data is scraped from clinic sites, names are reproduced verbatim as the clinic writes them, and the read date is a freshness signal because doctors move between practices.

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?

Three sentences, front-loaded with what is returned before the query guidance, and no filler. The 'date it was read' freshness point is made twice, which is mild redundancy but also reinforces an important caveat.

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 results, and it does list the returned fields: name, role, page, and read date. Query modes and the freshness caveat are covered; only the exact result structure and pagination remain unstated, which is acceptable for a lookup-style 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 coverage is 100%, so the schema already documents state, city, and doctor, including the two-letter-code/name flexibility and DC handling. The description reinforces the state/city pairing and the doctor-as-lookup-key behavior but adds no format or matching details beyond what the schema states, so baseline 3 applies.

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 names a specific resource and scope: the doctors US fertility clinics list on their own websites, with the role, page, and read date. That is clearly distinguishable from siblings like find_ivf_clinic_prices or clinics_taking_a_plan, which address pricing and plan acceptance rather than rosters.

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 spells out two concrete query modes: give a state (optionally a city) to get every clinic there that lists doctors, or give a doctor's name to find the clinic whose site lists that doctor. It falls short of naming a sibling alternative or stating exclusions, and it implies a state is expected even though the schema marks all three parameters optional.

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

All IVFcost.co: US IVF prices, coverage and grants toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources