Skip to main content
Glama

BreastPump.com Coverage Navigator

List carriers

list_carriers
Read-onlyIdempotent

Carriers with carrier-specific rules (commercial or marketplace), and whether each is verified.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond them: the result set is limited to carriers that have carrier-specific rules, split into commercial vs marketplace variants, and each entry carries a verified indicator. It still says nothing about ordering, size, or what 'verified' means, so it is useful but thin.

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?

A single short sentence with no filler, and the key scoping constraint is front-loaded. It loses a point only because the fragment lacks a verb and reads as a caption rather than a self-contained statement of what the tool does.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters, no output schema, and strong annotations, the bar is low, and the description covers scope and one returned field. It does not clarify the relationship to the sibling rule/coverage tools, which is the main thing an agent would need in order to choose correctly.

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 zero parameters with an empty schema, so there is no parameter semantics to explain; the baseline of 4 applies. The description correctly implies the filtering is fixed rather than caller-controlled.

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

Purpose3/5

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

The description is a noun fragment ('Carriers with carrier-specific rules...') that implies listing carriers, and it does specify the scope (only carriers that have carrier-specific rules, at commercial or marketplace level) plus the verified flag. However, it never states a verb such as 'list' or 'returns', and it gives no clue how it differs from siblings like get_state_rules or list_states beyond the resource noun.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no indication of when to call this instead of get_state_rules or check_coverage, and no preconditions. The reader must infer usage entirely from the resource name.

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