Sync by CHNLSYNC

Check copper retirement status

check_copper_retirement

Read-onlyIdempotent

Look up US copper/POTS retirement program status by carrier and state.

Deterministic read of CHNLSYNC's FCC-sourced dataset (CC BY 4.0 — cite the returned source_url). carrier accepts display names like "AT&T", "Lumen", "Frontier"; state is a two-letter abbreviation. Omit both for the full dataset.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`state`	No	Two-letter US state, e.g. TX.
`carrier`	No	Carrier display name, e.g. AT&T.

Output Schema

TableJSON Schema

Name	Required	Description
`as_of`	Yes	As-of date of static records, not of latest_filings.
`source`	Yes	Source methodology and limitations.
`license`	Yes	Reuse license; attribution is required.
`records`	Yes	Carrier/state entries matching the filters.
`source_url`	Yes	Attribution URL for the published dataset.
`latest_filings`	Yes	Up to 20 reviewed matching filings.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedSep 9, 2026

changedInput schema / properties / carrier / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 255,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / carrier / description
```
Added value: +"Carrier display name, e.g. AT&T."
```

changedInput schema / properties / state / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "pattern": "^[A-Za-z]{2}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / state / description
```
Added value: +"Two-letter US state, e.g. TX."
```

addedOutput schema / $defs

Added value: +{
+  "CopperFiling": {
+    "description": "One reviewed public filing with its own dates and primary-source link.",
+    "properties": {
+      "carrier": {
+        "description": "Carrier named by the filing.",
+        "title": "Carrier",
+        "type": "string"
+      },
+      "docket": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "FCC docket identifier, when available.",
+        "title": "Docket"
+      },
+      "filed_at": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Filing timestamp, when known.",
+        "title": "Filed At"
+      },
+      "filer": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Filing organization, when known.",
+        "title": "Filer"
+      },
+      "geography_detail": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Geographic scope from the source.",
+        "title": "Geography Detail"
+      },
+      "granted_at": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Grant timestamp, when known.",
+        "title": "Granted At"
+      },
+      "kind": {
+        "description": "Application, public notice, grant or carrier notice.",
+        "title": "Kind",
+        "type": "string"
+      },
+      "retirement_effective_at": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Effective date, when established.",
+        "title": "Retirement Effective At"
+      },
+      "source_url": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Primary-source filing URL, when available.",
+        "title": "Source Url"
+      },
+      "state": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "State when known; null is not nationwide coverage.",
+        "title": "State"
+      }
+    },
+    "required": [
+      "carrier",
+      "state",
+      "kind",
+      "filer",
+      "docket",
+      "filed_at",
+      "granted_at",
+      "retirement_effective_at",
+      "geography_detail",
+      "source_url"
+    ],
+    "title": "CopperFiling",
+    "type": "object"
+  },
+  "CopperRecord": {
+    "description": "State-level carrier program status, not an address-specific deadline.",
+    "properties": {
+      "carrier": {
+        "description": "Normalized carrier identifier.",
+        "title": "Carrier",
+        "type": "string"
+      },
+      "notes": {
+        "description": "Scope and limitations of the state-level entry.",
+        "title": "Notes",
+        "type": "string"
+      },
+      "retirement_date": {
+        "anyOf": [
+          {
+            "format": "date",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "Filed retirement date, or null when not established.",
+        "title": "Retirement Date"
+      },
+      "state": {
+        "description": "Two-letter US state abbreviation.",
+        "title": "State",
+        "type": "string"
+      },
+      "status": {
+        "description": "Program status.",
+        "enum": [
+          "date_filed",
+          "program_active"
+        ],
+        "title": "Status",
+        "type": "string"
+      }
+    },
+    "required": [
+      "carrier",
+      "state",
+      "retirement_date",
+      "status",
+      "notes"
+    ],
+    "title": "CopperRecord",
+    "type": "object"
+  }
+}

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / description

Added value: +"Citable program data and separately dated, reviewed filings."

addedOutput schema / properties

Added value: +{
+  "as_of": {
+    "anyOf": [
+      {
+        "format": "date",
+        "type": "string"
+      },
+      {
+        "type": "null"
+      }
+    ],
+    "description": "As-of date of static records, not of latest_filings.",
+    "title": "As Of"
+  },
+  "latest_filings": {
+    "description": "Up to 20 reviewed matching filings.",
+    "items": {
+      "$ref": "#/$defs/CopperFiling"
+    },
+    "title": "Latest Filings",
+    "type": "array"
+  },
+  "license": {
+    "const": "CC BY 4.0",
+    "description": "Reuse license; attribution is required.",
+    "title": "License",
+    "type": "string"
+  },
+  "records": {
+    "description": "Carrier/state entries matching the filters.",
+    "items": {
+      "$ref": "#/$defs/CopperRecord"
+    },
+    "title": "Records",
+    "type": "array"
+  },
+  "source": {
+    "description": "Source methodology and limitations.",
+    "title": "Source",
+    "type": "string"
+  },
+  "source_url": {
+    "description": "Attribution URL for the published dataset.",
+    "title": "Source Url",
+    "type": "string"
+  }
+}

addedOutput schema / required

Added value: +[
+  "records",
+  "source",
+  "source_url",
+  "license",
+  "as_of",
+  "latest_filings"
+]

addedOutput schema / title
```
Added value: +"CopperResponse"
```

First observedSep 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: deterministic output, FCC-sourced derivation, CC BY 4.0 licensing, and the requirement to cite the returned source_url.

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 core purpose, then the data provenance, then parameter guidance. Efficient overall, though the licensing/citation sentence is somewhat parenthetical and could be trimmed slightly.

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?

An output schema exists so return values need not be described, and the description still adds the source_url citation obligation that an agent would otherwise miss. For a two-optional-parameter read tool, nothing needed to call it correctly is absent.

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 the schema already gives examples ('TX', 'AT&T'), so the baseline is 3. The description reinforces the display-name and two-letter abbreviation formats and the omit-both behavior, but adds little beyond what the schema states.

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 (look up) plus resource (US copper/POTS retirement program status) and the two filtering dimensions. It is clearly distinguishable from the siblings ask_sync_advisor and request_broker_callback, which are unrelated functions.

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?

Explicitly tells the agent that omitting both parameters returns the full dataset, which is real when-to-use guidance. It does not name any alternative tool or state exclusions, but the siblings are unrelated so that omission costs little.

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

All Sync by CHNLSYNC tools Inspect

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

Need Help?