Skip to main content
Glama
RFingAdam

EMC Regulations MCP Server

by RFingAdam

fcc_cbrs_rules

Access FCC Part 96 CBRS rules for 3.5 GHz shared spectrum compliance with Citizens Broadband Radio Service regulations.

Instructions

Get FCC Part 96 CBRS (Citizens Broadband Radio Service) rules for 3.5 GHz shared spectrum.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function _cbrs_rules() that executes the 'fcc_cbrs_rules' tool logic. Retrieves Part 96 CBRS data from FCC_ADDITIONAL JSON and formats it with frequency, bandwidth, LTE/NR bands, access tiers (PAL/GAA), device categories, and SAS info.
    @staticmethod
    def _cbrs_rules() -> list[TextContent]:
        cbrs = FCC_ADDITIONAL.get("parts", {}).get("part_96", {})
    
        result = f"{cbrs.get('title', 'FCC Part 96 - CBRS')}\n{'=' * 55}\n\n"
        result += f"Frequency: {cbrs.get('frequency_mhz', [0, 0])[0]}-{cbrs.get('frequency_mhz', [0, 0])[1]} MHz\n"
        result += f"Bandwidth: {cbrs.get('bandwidth_mhz', '?')} MHz\n"
        result += f"LTE Bands: {', '.join(cbrs.get('lte_bands', []))}\n"
        result += f"NR Bands: {', '.join(cbrs.get('nr_bands', []))}\n\n"
    
        result += "## Access Tiers:\n"
        for tier_key, tier in cbrs.get("tiers", {}).items():
            result += f"\n  ### {tier.get('name', tier_key.title())}\n"
            result += f"  {tier['description']}\n"
            if tier.get("max_eirp_dbm_per_10mhz"):
                result += f"  Max EIRP: {tier['max_eirp_dbm_per_10mhz']} dBm/10MHz\n"
            if tier.get("notes"):
                result += f"  Notes: {tier['notes']}\n"
    
        result += "\n## Device Categories:\n"
        for cat_key, cat in cbrs.get("device_categories", {}).items():
            result += f"\n  {cat_key.replace('_', ' ').title()}: {cat['description']}\n"
            result += f"  Max EIRP: {cat['max_eirp_dbm_per_10mhz']} dBm/10MHz\n"
            if cat.get("notes"):
                result += f"  Notes: {cat['notes']}\n"
    
        sas = cbrs.get("sas", {})
        if sas:
            result += f"\n## Spectrum Access System (SAS):\n"
            result += f"  {sas['description']}\n"
            if sas.get("certified_administrators"):
                result += f"  Certified: {', '.join(sas['certified_administrators'])}\n"
    
        if cbrs.get("notes"):
            result += f"\n{cbrs['notes']}\n"
    
        return [TextContent(type="text", text=result)]
  • Tool registration in the list_tools() method of FCCTools class. Defines the 'fcc_cbrs_rules' tool with name, description, and empty input schema.
        Tool(
            name="fcc_cbrs_rules",
            description="Get FCC Part 96 CBRS (Citizens Broadband Radio Service) rules for 3.5 GHz shared spectrum.",
            inputSchema={"type": "object", "properties": {}},
        ),
    ]
  • Input schema for 'fcc_cbrs_rules' — an empty object (no parameters required).
    inputSchema={"type": "object", "properties": {}},
  • Dispatch in call_tool() method routing the 'fcc_cbrs_rules' tool name to the _cbrs_rules() handler.
    elif name == "fcc_cbrs_rules":
        return self._cbrs_rules()
  • Loading of the fcc_additional_parts.json data file which contains the Part 96 CBRS rules data used by _cbrs_rules().
    PART15_LIMITS = load_json("part15_limits.json")
    PART18_LIMITS = load_json("part18_limits.json")
    RESTRICTED_BANDS = load_json("restricted_bands.json")
    FCC_ADDITIONAL = load_json("fcc_additional_parts.json")
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It states only that the tool 'gets' rules, but omits details about data freshness, authentication, rate limits, or output format. The agent lacks insight into how the tool operates beyond its topic.

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?

The description is a single, efficient sentence that directly states the tool's purpose with no extraneous words. It is perfectly front-loaded and earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (no params, no output schema), the description is minimally adequate. It tells the agent what the tool provides but lacks details on the output format or any hidden complexities. For a server with many similar rule-lookup tools, a bit more context about the returned data would improve completeness.

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?

The input schema has zero parameters, so schema description coverage is 100% (trivially). Per guidelines, 0 params yields a baseline of 4. The description adds the specific context of Part 96 and CBRS, which is meaningful beyond the empty schema.

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 specifies the action 'Get' and the exact resource 'FCC Part 96 CBRS rules for 3.5 GHz shared spectrum', distinguishing it from similar sibling tools like fcc_part15_limit or fcc_part95_limits by naming the specific part.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus other FCC part limit tools (e.g., fcc_part15_limit, fcc_part95_limits). It does not mention context, prerequisites, or typical use cases beyond simply stating the topic.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RFingAdam/mcp-emc-regulations'

If you have feedback or need assistance with the MCP directory API, please join our Discord server