Skip to main content
Glama
Sign In

DocketTrail

by com.dockettrail
OverviewDiscussionsAdmin

List changes

list_changes
Read-onlyIdempotent

What changed, newest first: new proceedings, the agency's wording changed (before and after, verbatim), new events, new documents. Dated by the day DocketTrail observed the change on a check of the agency's page, not the day it happened. Without a key: the last 30 days, filtered by state, program and kind. A founding key reads the full history and adds org, agency, q and since. 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": "list_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFounding key only. A keyword, matched as a substring of the parties as filed, the agency title and status, and the agency name.
orgNoFounding key only. An organization slug, from find_organization.
kindNoRECORD_ADDED, STATUS_CHANGED (the agency wording changed), EVENT_ADDED (an agency action; a deadline, or a date the agency printed for the future, is not a change), NOTE_CHANGED (a note or document) or RETYPESET (the agency re-typeset its wording: spacing or dashes only; listed only when asked for).
pageNoPage number, from 1.
sinceNoFounding key only. A date, yyyy-mm-dd (UTC): only what DocketTrail observed changing on or after that day.
stateNoTwo-letter state code: OR, CA, MA, WA, IA, IL, FL, NC, HI, MO, GA, SC, VA, KY, DE, NM, DC, MN.
agencyNoFounding key only. An agency slug: the agency's name, lower-case and hyphenated.
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.
per_pageNoRecords per page. Default 25; 25 is the most without a founding key, 200 with one.

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. Changed1 schema field changed
    • changedInput schema / properties / kind / description
      Previous value: -"RECORD_ADDED, STATUS_CHANGED (the agency wording changed), EVENT_ADDED, DEADLINE_ADDED (a deadline or scheduled date the agency printed, such as a letter of intent expiry or a hearing date; listed only when asked for), NOTE_CHANGED (a note or document) or RETYPESET (the agency re-typeset its wording: spacing or dashes only; listed only when asked for)."New value: +"RECORD_ADDED, STATUS_CHANGED (the agency wording changed), EVENT_ADDED (an agency action; a deadline, or a date the agency printed for the future, is not a change), NOTE_CHANGED (a note or document) or RETYPESET (the agency re-typeset its wording: spacing or dashes only; listed only when asked for)."
  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, 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."
  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, 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."
  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, 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."
  12. 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."
  13. Changed1 schema field changed
    • changedInput schema / properties / kind / description
      Previous value: -"RECORD_ADDED, STATUS_CHANGED (the agency wording changed), EVENT_ADDED, NOTE_CHANGED (a note or document) or RETYPESET (the agency re-typeset its wording: spacing or dashes only; listed only when asked for)."New value: +"RECORD_ADDED, STATUS_CHANGED (the agency wording changed), EVENT_ADDED, DEADLINE_ADDED (a deadline or scheduled date the agency printed, such as a letter of intent expiry or a hearing date; listed only when asked for), NOTE_CHANGED (a note or document) or RETYPESET (the agency re-typeset its wording: spacing or dashes only; listed only when asked for)."
  14. 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."
  15. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint, destructiveHint=false, idempotentHint, openWorldHint=false), and the description adds substantive behavior beyond them: results are dated by the day DocketTrail observed the change rather than the day it happened, a RETYPESET class exists but is hidden unless asked for, coverage is limited to specific states and record types, and absence of data is explicitly not a claim that no review exists. It also discloses the provenance fields returned (source_url, observed_day, first_seen_at, last_checked_at) and the non-legal-advice caveat.

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 most decision-relevant content — what a change is and that dates are observation dates — is front-loaded, which is good. However it is a single dense block in which the coverage state lists duplicate the state and program enums in the schema, and the coverage URL plus legal disclaimer add bulk that could be tightened without losing routing value.

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 return-value burden and does so for the key fields (source_url, observed_day, first_seen_at, last_checked_at, verbatim before/after wording). It does not describe the response envelope or pagination metadata beyond the per_page/page parameters, so it is strong but not fully exhaustive for a 9-parameter list 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 description coverage is 100%, so the baseline is 3. The description's parameter information ('Without a key: the last 30 days, filtered by state, program and kind' and the founding-key-only list 'org, agency, q and since') largely restates what each schema property already says, adding only the tier grouping rather than new per-parameter meaning.

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 opening clause names the exact resource and ordering: 'What changed, newest first: new proceedings, the agency's wording changed (before and after, verbatim), new events, new documents.' That is a specific verb-plus-resource definition (a change feed) that an agent can distinguish from search_proceedings, get_proceeding, review_stats and find_organization without opening any schema.

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 states the access tiers that govern usage ('Without a key: the last 30 days, filtered by state, program and kind. A founding key reads the full history and adds org, agency, q and since') and scopes the data to three review types across named states. It never names a sibling tool as the alternative for a different need, so there is clear context but no explicit when-not guidance.

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