Skip to main content
Glama

Fcc Regulations

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Fcc Regulations Search

fcc_regulations_search
Read-onlyIdempotent

Keyword search across the FCC regulations — US telecommunications rules in 47 CFR. Answers "what FCC regulations cover X", "the FCC rule about X", "find the telecommunications regulation for X", "which radio / spectrum / wireless rule applies to X". Great for topics: unlicensed device emission limits, Part 15 intentional and unintentional radiators, RF exposure and radiofrequency radiation limits, equipment authorization and certification, amateur radio operating privileges, spectrum and frequency allocations, broadcast station licensing and ownership, cable and satellite carriage, robocalls and caller ID, 911 and emergency alerting, wireless and common carrier obligations. Returns matching FCC rules with citation (47 CFR), heading, excerpt, and source URL. Example: fcc_regulations_search({ query: "unlicensed device emission limits" }); fcc_regulations_search({ query: "amateur radio frequency bands", limit: 15 }). Keyless. Searches the FCC RULES text; the separate fcc and data-fcc packs search FCC filings and licensing data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results to return, 1-20 (default 10).
queryYesTelecommunications-regulation topic or phrase, e.g. "unlicensed device emission limits", "RF exposure", "equipment authorization", "amateur radio frequency bands", "broadcast ownership".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "unlicensed device emission limits"
+  },
+  {
+    "limit": 15,
+    "query": "RF exposure limits"
+  }
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint false. The description adds return format details (citation, heading, excerpt, source URL) and mentions 'Keyless' (no API key). It is consistent with annotations and adds useful context beyond them.

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 description is long but well-structured: purpose first, then examples, then differentiation. Every sentence contributes information. Minor verbosity but acceptable for the detail needed.

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?

Despite no output schema, the description specifies return fields (citation, heading, excerpt, source URL). It covers which data is searched (rules) and what is not (filings). For a search tool, this is complete and actionable.

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

Parameters4/5

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

Schema coverage is 100% with descriptions for both parameters. The description adds value through concrete query examples and states the default limit (10). This supports correct invocation.

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 it performs keyword search across FCC regulations (47 CFR). It provides specific examples and distinguishes from sibling tools like fcc_regulation and fcc packs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives extensive example queries, topics, and explicit differentiation from other tools: 'Searches the FCC RULES text; the separate fcc and data-fcc packs search FCC filings and licensing data.' This clearly tells the agent when to use this tool.

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

All Fcc Regulations toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources