Skip to main content
Glama
RFingAdam

EMC Regulations MCP Server

by RFingAdam

fcc_restricted_bands

Check if a frequency falls within FCC Part 15.205 restricted bands for regulatory compliance.

Instructions

Check if a frequency falls within FCC Part 15.205 restricted bands.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frequency_mhzYesFrequency in MHz to check

Implementation Reference

  • Tool 'fcc_restricted_bands' is registered in FCCTools.list_tools() with its name, description, and inputSchema requiring frequency_mhz.
    Tool(
        name="fcc_restricted_bands",
        description="Check if a frequency falls within FCC Part 15.205 restricted bands.",
        inputSchema={
            "type": "object",
            "properties": {
                "frequency_mhz": {"type": "number", "description": "Frequency in MHz to check"},
            },
            "required": ["frequency_mhz"],
        },
    ),
  • Dispatcher in FCCTools.call_tool() that routes 'fcc_restricted_bands' to _restricted_bands() handler.
    elif name == "fcc_restricted_bands":
        return self._restricted_bands(arguments)
  • The _restricted_bands() handler that checks if a given frequency falls within an FCC Part 15.205 restricted band by calling check_restricted_band() and returning a human-readable result.
    @staticmethod
    def _restricted_bands(arguments: dict[str, Any]) -> list[TextContent]:
        freq_mhz = arguments["frequency_mhz"]
        restricted = check_restricted_band(freq_mhz)
    
        if restricted:
            result = "\u26a0\ufe0f  RESTRICTED BAND\n\n"
            result += f"Frequency {freq_mhz} MHz falls within a restricted band per 47 CFR 15.205:\n\n"
            result += f"  Band: {restricted['freq_min_mhz']} - {restricted['freq_max_mhz']} MHz\n"
            result += f"  Protected Service: {restricted['service']}\n\n"
            result += "Intentional radiators are generally prohibited from operating in this band."
        else:
            result = f"\u2713 CLEAR\n\nFrequency {freq_mhz} MHz is NOT in a restricted band."
    
        return [TextContent(type="text", text=result)]
  • Helper check_restricted_band() that iterates over RESTRICTED_BANDS data to determine if a frequency falls in any restricted band range.
    def check_restricted_band(freq_mhz: float) -> dict | None:
        """Check if frequency is in a restricted band."""
        for band in RESTRICTED_BANDS.get("restricted_bands", []):
            if band["freq_min_mhz"] <= freq_mhz <= band["freq_max_mhz"]:
                return band
        return None
  • Loading of RESTRICTED_BANDS data from 'restricted_bands.json' JSON file used by the helper and handler.
    RESTRICTED_BANDS = load_json("restricted_bands.json")
Behavior2/5

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

No annotations are provided, and the description does not disclose what the tool returns (e.g., boolean, status message) or any side effects. For a checklist tool, the behavioral expectation is minimal, but lack of output specification is a gap.

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, concise sentence that effectively communicates the tool's function without unnecessary detail.

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 the simplicity (one required parameter, no output schema, no nested objects), the description is mostly complete. It could be improved by indicating the output format, but for a straightforward check, it suffices.

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 coverage is 100% with a description for 'frequency_mhz'. The tool description adds context about the purpose (checking restricted bands) but does not provide additional semantics beyond the schema's parameter description.

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 uses a clear action verb ('Check') and identifies the specific resource ('frequency within FCC Part 15.205 restricted bands'), distinguishing it from siblings like 'fcc_restricted_bands_list' which list the bands rather than check a single frequency.

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 does not explicitly state when to use this tool versus alternatives, such as when to check a single frequency vs. retrieving the full list of restricted bands. However, the purpose is clear enough for a simple query.

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