Skip to main content
Glama
Sign In

GPH Intelligence - Healthcare Vendor Finder

by io.github.Crindo2
OverviewDiscussionsAdmin

Practice Data Counts

practice_data_counts
Read-onlyIdempotent

Counts practices with headline (strongest-tier) evidence only, by US state and practice segment, from the public Practice Data aggregate endpoint (unit: practices (headline evidence)). It excludes lower-evidence records, so these numbers are lower than the all-record totals on the Practice Data product pages (507,423 nationally as published there). Cells with fewer than 25 practices are not published (returned with count null and suppressed true). Aggregate counts only: no records or names are returned. Optional state and segment filters narrow the result; the JSON body is returned unchanged.

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

Input Schema

NameRequiredDescriptionDefault
stateNoOptional two-letter capital US state code, e.g. TX.
segmentNoOptional practice segment slug, one of the six served by the endpoint, e.g. primary-care.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, it discloses real behavioral traits: suppression of cells under 25 practices with count null and suppressed true, exclusion of lower-evidence records causing lower totals than the product pages, and an unchanged JSON passthrough body. These are exactly the surprises an agent would otherwise hit at runtime.

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?

The core definition (headline-only counts, by state and segment) is front-loaded, and the suppression caveat follows immediately. It is dense but nearly every clause carries operational value; the parenthetical national total is helpful context rather than filler.

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 takes on the burden of explaining returns and does so for the important cases: aggregate counts, null/suppressed cells, and a raw JSON body. It does not enumerate the response's field layout, leaving some ambiguity about what the unchanged body actually contains.

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% and both parameters are documented in-schema, including the enum and the state pattern, so the baseline is 3. The description only adds that state and segment are optional narrowing filters, which is modest reinforcement rather than new semantics.

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 gives a specific verb and resource ("Counts practices with headline (strongest-tier) evidence only, by US state and practice segment") plus the endpoint it reads from and the unit of measure. That is clearly distinguishable from the sibling detail/search tools (get_provider_detail, search_providers, match_practice), none of which return aggregate counts.

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 establishes the context for use by ruling out record-level output ("Aggregate counts only: no records or names are returned"), which steers an agent toward the search/detail siblings when names are needed. It never names a sibling or states an explicit when-not condition, so it stops short of full alternative routing.

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

All GPH Intelligence - Healthcare Vendor Finder 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