Skip to main content
Glama
RFingAdam

EMC Regulations MCP Server

by RFingAdam

lte_bands_list

List LTE bands filtered by region (Americas, Europe, APAC, Global) or US carrier (AT&T, Verizon, T-Mobile).

Instructions

List all LTE bands, optionally filtered by region or carrier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionNoFilter by region (Americas, Europe, APAC, Global)
carrierNoFilter by US carrier (att, verizon, tmobile)

Implementation Reference

  • Handler for lte_bands_list tool: filters by region or carrier, returns formatted list of LTE bands (up to 30).
    @staticmethod
    def _lte_bands_list(arguments: dict[str, Any]) -> list[TextContent]:
        region = arguments.get("region", "").lower()
        carrier = arguments.get("carrier", "").lower()
    
        if carrier:
            carrier_bands = LTE_BANDS.get("us_carrier_bands", {}).get(carrier, {})
            if carrier_bands:
                result = f"LTE Bands for {carrier.upper()}\n{'=' * 40}\n\n"
                result += f"Primary bands: {', '.join(str(b) for b in carrier_bands.get('primary', []))}\n"
                result += f"LTE-M bands:   {', '.join(str(b) for b in carrier_bands.get('lte_m', []))}\n"
            else:
                result = f"Carrier '{carrier}' not found. Available: att, verizon, tmobile"
        else:
            bands = LTE_BANDS.get("bands", [])
            if region:
                bands = [b for b in bands if region in [r.lower() for r in b.get("regions", [])]]
    
            result = f"LTE Bands{' (' + region.title() + ')' if region else ''}\n{'=' * 50}\n\n"
            for band in bands[:30]:
                ul = band.get("uplink_mhz", [0, 0])
                dl = band.get("downlink_mhz", [0, 0])
                result += f"Band {band['band']:>2}: {dl[0]:>4}-{dl[1]:<4} MHz ({band['duplex']}) {band.get('name', '')}\n"
    
        return [TextContent(type="text", text=result)]
  • Tool schema definition listing input parameters: region (optional string) and carrier (optional string).
    Tool(
        name="lte_bands_list",
        description="List all LTE bands, optionally filtered by region or carrier.",
        inputSchema={
            "type": "object",
            "properties": {
                "region": {"type": "string", "description": "Filter by region (Americas, Europe, APAC, Global)"},
                "carrier": {"type": "string", "description": "Filter by US carrier (att, verizon, tmobile)"},
            },
        },
  • Routes the 'lte_bands_list' tool name to the _lte_bands_list handler method.
    elif name == "lte_bands_list":
        return self._lte_bands_list(arguments)
  • ToolRegistry auto-discovers CellularTools via _discover() which iterates over all modules in the tools package and instantiates ToolModule subclasses.
    def __init__(self) -> None:
        self._modules: list[ToolModule] = []
        self._discover()
    
    # ------------------------------------------------------------------
    # Public API used by server.py
    # ------------------------------------------------------------------
    
    def list_tools(self) -> list[Tool]:
        result: list[Tool] = []
        for mod in self._modules:
            result.extend(mod.list_tools())
        return result
    
    async def call_tool(self, name: str, arguments: dict[str, Any]) -> list[TextContent]:
        for mod in self._modules:
            if mod.handles(name):
                return await mod.call_tool(name, arguments)
        return [TextContent(type="text", text=f"Unknown tool: {name}")]
    
    # ------------------------------------------------------------------
    # Auto-discovery
    # ------------------------------------------------------------------
    
    def _discover(self) -> None:
        """Import every module in the ``tools`` package and instantiate ToolModules."""
        for info in pkgutil.iter_modules(_tools_pkg.__path__, _tools_pkg.__name__ + "."):
            module = importlib.import_module(info.name)
            for attr_name in dir(module):
                attr = getattr(module, attr_name)
                if (
                    isinstance(attr, type)
                    and issubclass(attr, ToolModule)
                    and attr is not ToolModule
                ):
                    self._modules.append(attr())
  • Utility that loads the lte_bands.json data file used by _lte_bands_list to retrieve band information.
    def load_json(filename: str) -> dict:
        """Load a JSON data file from the package data directory."""
        filepath = DATA_DIR / filename
        if filepath.exists():
            return json.loads(filepath.read_text())
        return {}
Behavior2/5

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It does not mention whether the operation is read-only, side effects, or default behavior (e.g., all bands if no filters). For a list tool, such details are important.

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 with no wasted words. It is front-loaded with the core 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?

For a simple list tool with two optional filters, the description is adequate but could be enhanced with information about return format, default behavior, or relationship to sibling tools. No output schema exists, so the description leaves some gaps.

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 clear descriptions for both parameters. The description adds 'optionally filtered' but does not provide additional meaning beyond the schema's parameter descriptions.

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' and the resource 'LTE bands', with optional filters for region or carrier. It distinguishes from siblings like 'lte_band_lookup' (which is for a specific band) and 'nr_bands_list' (for a different band type).

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 use for listing bands with optional filtering but does not explicitly state when to use this tool versus alternatives like 'lte_band_lookup' or 'nr_bands_list'. No exclusion criteria are given.

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