Skip to main content
Glama
Sign In

Fcc Ecfs

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ecfs Docket Filings

ecfs_docket_filings
Read-onlyIdempotent

List FCC ECFS filings in an exact proceeding/docket, newest first, including documents and parties. A filing reflects the submitter’s position and is not an FCC decision.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 25,
      "proceeding": "11-42"
    },
    "name": "ecfs_docket_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
_apiKeyNoOptional api.data.gov key for higher limits; defaults to DEMO_KEY.
proceedingYesExact docket/proceeding number, e.g. 11-42.

Output Schema

NameRequiredDescriptionDefault
sourceYes
filingsYes
returnedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the agent knows it is safe and non-destructive. The description adds valuable context: filings reflect the submitter's position and are not FCC decisions, and they are listed newest first.

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

Conciseness5/5

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

Two sentences, no fluff. The first sentence states the core purpose, and the second adds an important nuance about the nature of filings. Every sentence earns its place.

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?

Given that an output schema exists (so return values are covered), the description is mostly complete. It could mention pagination via limit/offset, but the 'newest first' ordering and inclusion of documents/parties are noted. A minor gap is the lack of pagination hint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50%: only proceeding and _apiKey have descriptions. The tool description does not explain limit and offset, nor does it add meaning beyond what the schema already provides. The description lacks any parameter-specific guidance.

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 clearly states the verb 'List', the resource 'FCC ECFS filings', and the specific context 'in an exact proceeding/docket, newest first'. It distinguishes this tool from siblings like ecfs_search_filings and ecfs_filing_detail by focusing on a specific docket.

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?

The description implies usage when an exact proceeding number is known, but it does not explicitly state when to use this tool versus alternatives like ecfs_search_filings (for searching) or ecfs_filing_detail (for a single filing). No guidance on prerequisites or limitations.

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

All Fcc Ecfs 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