Skip to main content
Glama
RFingAdam

EMC Regulations MCP Server

by RFingAdam

fcc_part18_limit

Retrieve FCC Part 18 emission limits for ISM equipment by specifying frequency and equipment type to verify compliance.

Instructions

Get FCC Part 18 (ISM equipment) emission limits. Check ISM bands and limits for industrial/consumer ISM equipment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frequency_mhzYesFrequency in MHz
equipment_typeNoISM equipment type

Implementation Reference

  • Handler function _part18_limit that executes the fcc_part18_limit tool logic: checks if the frequency is within an ISM band, then looks up Part 18.305 emission limits outside ISM bands based on equipment type (consumer/industrial).
    @staticmethod
    def _part18_limit(arguments: dict[str, Any]) -> list[TextContent]:
        freq_mhz = arguments["frequency_mhz"]
        eq_type = arguments.get("equipment_type", "consumer")
    
        result = f"FCC Part 18 (ISM Equipment) at {freq_mhz} MHz\n{'=' * 50}\n\n"
    
        ism_band = check_ism_band(freq_mhz)
        if ism_band:
            result += "\u2713 WITHIN ISM BAND\n"
            result += f"  Center: {ism_band['center_mhz']} MHz\n"
            result += f"  Range: {ism_band['range_mhz'][0]} - {ism_band['range_mhz'][1]} MHz\n"
            if "notes" in ism_band:
                result += f"  Notes: {ism_band['notes']}\n"
            result += "  Fundamental emissions: No limit within ISM band\n"
        else:
            result += "\u2717 OUTSIDE ISM BANDS\n"
            result += "  Standard emission limits apply (same as Part 15.209)\n\n"
    
        sec_data = PART18_LIMITS.get("section_18_305", {})
        eq_data = sec_data.get(f"{eq_type}_ism", {})
        limits = eq_data.get("emissions_outside_ism", [])
        limit = find_limit_for_frequency(limits, freq_mhz)
    
        if limit:
            result += f"\nLimits outside ISM bands ({eq_type.title()} ISM):\n"
            result += format_limit_result(limit)
    
        return [TextContent(type="text", text=result)]
  • Schema definition for the fcc_part18_limit tool in list_tools(), defining input parameters: frequency_mhz (required number) and equipment_type (optional string with enum consumer/industrial).
    Tool(
        name="fcc_part18_limit",
        description="Get FCC Part 18 (ISM equipment) emission limits. Check ISM bands and limits for industrial/consumer ISM equipment.",
        inputSchema={
            "type": "object",
            "properties": {
                "frequency_mhz": {"type": "number", "description": "Frequency in MHz"},
                "equipment_type": {"type": "string", "enum": ["consumer", "industrial"], "description": "ISM equipment type"},
            },
            "required": ["frequency_mhz"],
        },
    ),
  • Dispatch in call_tool() routing tool name "fcc_part18_limit" to the _part18_limit handler method.
    elif name == "fcc_part18_limit":
        return self._part18_limit(arguments)
  • Helper function check_ism_band used by _part18_limit to check if a frequency falls within any ISM band defined in the part18_limits.json data.
    def check_ism_band(freq_mhz: float) -> dict | None:
        """Check if frequency is in an ISM band."""
        for band in PART18_LIMITS.get("ism_bands", {}).get("bands", []):
            range_mhz = band.get("range_mhz", [0, 0])
            if range_mhz[0] <= freq_mhz <= range_mhz[1]:
                return band
        return None
Behavior3/5

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

No annotations provided; description assumes a read-only query operation, but does not explicitly state non-destructive behavior or handle edge cases like out-of-range frequencies.

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 front-loaded sentences with zero waste, effectively conveying the tool's purpose.

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 no output schema, description could hint at return format (e.g., limit values) or behavior for missing parameters, but it's adequate for a simple query tool.

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 descriptions for both parameters. Description reinforces equipment_type context but adds no new meaning beyond the 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?

Description uses specific verb 'Get' and resource 'FCC Part 18 emission limits', clearly distinguishing from siblings like fcc_part15_limit or ism_bands_list.

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?

Description implies use for checking limits on ISM equipment, but does not explicitly state when not to use or compare with similar siblings like ism_bands_list.

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