Skip to main content
Glama

BreastPump.com Coverage Navigator

Check breast pump coverage

check_coverage
Read-onlyIdempotent

Explain whether a US family's insurance covers a breast pump: pump types, when to order, Rx rule, next steps, one coverage CTA (paid only for eligible commercial/Marketplace results, and flagged), sources and verification status. Uninsured results list official coverage paths. Any paid referral appears only in the separate sponsored_next_steps array, which is off by default. Don't send personal data.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "state": "<state>",
      "insurance_type": "<insurance_type>"
    },
    "name": "check_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes2-letter US state code or name, e.g. TX. DC is supported.
carrierNoOptional carrier, for commercial or marketplace: uhc, aetna, cigna, bcbs, kaiser, or a name like 'Anthem'
due_dateNoOptional YYYY-MM-DD. A past date is treated as the baby's birth date.
insurance_typeYesPlan type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing monetization behavior: the single CTA is paid only for eligible commercial/Marketplace results, is flagged, and any paid referral appears solely in the separate sponsored_next_steps array which is off by default. It also states what happens for uninsured results and that sources plus verification status are returned — exactly the kind of output-side behavior an agent cannot infer from structured fields.

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?

Front-loaded with the purpose in the first clause, and the dense enumeration of returned content is informative rather than filler. The middle of the passage packs eligibility conditions, flagging, and the sponsored array into one long run-on sentence, which slightly hurts scannability but each clause carries real information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 full burden and meets it: it names the returned sections (pump types, when to order, Rx rule, next steps, CTA, sources, verification status) and the separate sponsored_next_steps array. Combined with the explicit uninsured-path behavior and the no-personal-data rule, an agent has enough to call this correctly.

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 description coverage is 100%, so state, carrier, due_date, and insurance_type are already fully documented, and the description adds no format or syntax detail beyond them. It does add one semantic note — the 'US family' framing and the instruction not to send personal data — which reinforces how to populate inputs but does not deepen any individual parameter.

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?

States a specific verb and resource: 'Explain whether a US family's insurance covers a breast pump', then enumerates the answer contents (pump types, when to order, Rx rule, next steps). This is clearly distinguishable from the reference-style siblings get_state_rules, list_carriers, and list_states, which cannot answer a family-specific coverage question.

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 implied by the description's framing (a family asking about their own coverage) and by the 'Uninsured results list official coverage paths' behavior, but there is no explicit routing such as 'use list_carriers to discover valid carrier values first' or 'use get_state_rules for statute text rather than a family-specific answer'. The one hard constraint given is 'Don't send personal data', which is a useful guardrail rather than when-to-use guidance.

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