Skip to main content
Glama
Sign In

DocketTrail

by com.dockettrail
OverviewDiscussionsAdmin

How reviews go

review_stats
Read-onlyIdempotent

How reviews end and how long they take, computed from the records: per program, outcomes in the agency's own words with counts, shares (waived, taken to a cost and market impact review, approved with conditions, follow-up reviews) and durations in days (median, 25th to 75th percentile, range, n) over proceedings carrying both agency dates; deals reviewed in more than one state; the organizations in the most proceedings. Where n is under 5 the cases are listed instead of a median. Each figure names the list (href) behind it; the method is at https://dockettrail.com/stats#method. Every result points at the records it was computed from (href), each of which carries its source_url. Nothing is estimated or predicted. Covers healthcare transaction reviews (OR, CA, MA, NM, WA, MN), certificate-of-need projects (WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY, DE, DC) and nonprofit health facility notices (CA, GA) only (see https://dockettrail.com/coverage for what is tracked and what was checked and not tracked). Every result is a public agency record, in the agency's own words, with source_url (the agency page it was read from) and the day DocketTrail observed it (observed_day, first_seen_at, last_checked_at; UTC). Nothing here is legal advice, and absence from the data is not a claim that no review exists.

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

Input Schema

NameRequiredDescriptionDefault
stateNoTwo-letter state code: OR, CA, MA, WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY, DE, NM, DC, MN.
programNoA program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn, ky-con, de-cpr, nm-hca, dc-con, wa-ag, ga-ag, mn-ag) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / program / description
      Previous value: -"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn, ky-con, de-cpr, nm-hca, dc-con, wa-ag, ga-ag) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."New value: +"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn, ky-con, de-cpr, nm-hca, dc-con, wa-ag, ga-ag, mn-ag) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter state code: OR, CA, MA, WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY, DE, NM, DC."New value: +"Two-letter state code: OR, CA, MA, WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY, DE, NM, DC, MN."
  2. Changed1 schema field changed
    • changedInput schema / properties / program / description
      Previous value: -"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn, ky-con, de-cpr, nm-hca, dc-con, wa-ag) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."New value: +"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn, ky-con, de-cpr, nm-hca, dc-con, wa-ag, ga-ag) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."
  3. Changed1 schema field changed
    • changedInput schema / properties / program / description
      Previous value: -"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn, ky-con, de-cpr, nm-hca, dc-con) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."New value: +"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn, ky-con, de-cpr, nm-hca, dc-con, wa-ag) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."
  4. Changed2 schema fields changed
    • changedInput schema / properties / program / description
      Previous value: -"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn, ky-con, de-cpr, nm-hca) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."New value: +"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn, ky-con, de-cpr, nm-hca, dc-con) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter state code: OR, CA, MA, WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY, DE, NM."New value: +"Two-letter state code: OR, CA, MA, WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY, DE, NM, DC."
  5. Changed2 schema fields changed
    • changedInput schema / properties / program / description
      Previous value: -"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn, ky-con, de-cpr) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."New value: +"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn, ky-con, de-cpr, nm-hca) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter state code: OR, CA, MA, WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY, DE."New value: +"Two-letter state code: OR, CA, MA, WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY, DE, NM."
  6. Changed2 schema fields changed
    • changedInput schema / properties / program / description
      Previous value: -"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn, ky-con) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."New value: +"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn, ky-con, de-cpr) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter state code: OR, CA, MA, WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY."New value: +"Two-letter state code: OR, CA, MA, WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY, DE."
  7. Changed2 schema fields changed
    • changedInput schema / properties / program / description
      Previous value: -"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."New value: +"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn, ky-con) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter state code: OR, CA, MA, WA, IA, IL, FL, NC, HI, MO, GA, SC, VA."New value: +"Two-letter state code: OR, CA, MA, WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY."
  8. Changed2 schema fields changed
    • changedInput schema / properties / program / description
      Previous value: -"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."New value: +"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con, va-copn) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter state code: OR, CA, MA, WA, IA, IL, FL, NC, HI, MO, GA, SC."New value: +"Two-letter state code: OR, CA, MA, WA, IA, IL, FL, NC, HI, MO, GA, SC, VA."
  9. Changed2 schema fields changed
    • changedInput schema / properties / program / description
      Previous value: -"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."New value: +"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag, nc-con, hi-con, mo-con, ga-con, sc-con) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter state code: OR, CA, MA, WA, IA, IL, FL."New value: +"Two-letter state code: OR, CA, MA, WA, IA, IL, FL, NC, HI, MO, GA, SC."
  10. Changed2 schema fields changed
    • changedInput schema / properties / program / description
      Previous value: -"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, fl-con) or a record type (transaction-review, certificate-of-need). Free, like state."New value: +"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, il-con, fl-con, ca-ag) or a record type (transaction-review, certificate-of-need, nonprofit-hospital-notice). Free, like state."
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter state code: OR, CA, MA, WA, IA, FL."New value: +"Two-letter state code: OR, CA, MA, WA, IA, IL, FL."
  11. Changed2 schema fields changed
    • changedInput schema / properties / program / description
      Previous value: -"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con) or a record type (transaction-review, certificate-of-need). Free, like state."New value: +"A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con, fl-con) or a record type (transaction-review, certificate-of-need). Free, like state."
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter state code: OR, CA, MA, WA, IA."New value: +"Two-letter state code: OR, CA, MA, WA, IA, FL."
  12. Changed2 schema fields changed
    • addedInput schema / properties / program
      Added value: +{
+  "description": "A program id (or-hcmo, ca-ohca, ma-hpc, wa-con, ia-con) or a record type (transaction-review, certificate-of-need). Free, like state.",
+  "type": "string"
+}
    • changedInput schema / properties / state / description
      Previous value: -"Two-letter state code: OR, CA or MA."New value: +"Two-letter state code: OR, CA, MA, WA, IA."
  13. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, closed-world safety, and the description adds substantial behavior beyond that: the small-sample suppression rule (cases listed instead of a median when n<5), the n-per-figure disclosure, the href linkage back to underlying records and their source_url, the provenance timestamps (observed_day, first_seen_at, last_checked_at), the 'nothing is estimated' guarantee, and an explicit coverage boundary with a caveat that absence is not evidence of no review.

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

Conciseness3/5

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

The purpose is front-loaded and the content is information-dense, but the block is a single sprawling paragraph that repeats itself: record provenance is described twice ('Every result points at the records it was computed from' and 'Every result is a public agency record... with source_url'), and the closing disclaimer stack adds length. Tighter grouping of output shape, coverage limits, and caveats would read better.

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 does the work of explaining the return shape — outcome categories, counts, shares, duration statistics, and per-figure record links — which is the right call. Coverage boundaries and the method link round it out. Minor gaps remain around default behavior with no filters and result volume, but the tool is well covered overall.

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%, and both parameters already enumerate their allowed values, so the schema carries the weight. The description adds only marginal meaning — it restates the state coverage in prose and implies 'per program' grouping — without explaining interaction between the two filters or default behavior when both are absent. Baseline 3 is appropriate.

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 opens with a specific statement of what is computed: 'How reviews end and how long they take, computed from the records,' then enumerates the concrete outputs (outcomes, shares, durations, multi-state deals, top organizations). This clearly separates it from siblings like get_proceeding or search_proceedings, which return individual records, though it never names those alternatives explicitly.

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 nature of the output ('computed from the records', aggregate figures). There is no explicit 'use this when you want statistics rather than a single proceeding' routing against the siblings, and no statement about what happens if state/program are omitted. The n<5 rule and the coverage-scope sentence do help an agent judge whether this tool will answer a given question.

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

All DocketTrail 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