Skip to main content
Glama
Sign In
EMC Regulations MCP Server

EMC Regulations MCP Server

by RFingAdam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

fcc_restricted_bands_list

Retrieve FCC Part 15.205 restricted frequency bands with optional min/max frequency filtering for compliance checks.

Instructions

List all FCC Part 15.205 restricted frequency bands.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "fcc_restricted_bands_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
freq_min_mhzNoOnly show bands above this frequency
freq_max_mhzNoOnly show bands below this frequency

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, and the description only says 'List all...' without disclosing behavioral traits. It does not mention that it is read-only, nor does it describe output format or pagination.

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 a single clear sentence with no wasted words. However, it could be slightly improved by adding more structure.

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

Completeness2/5

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

Given the lack of output schema and sibling ambiguity, the description is incomplete. It does not explain what the returned data looks like or how to interpret results.

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 adequate parameter descriptions. The tool description adds no extra semantic value beyond the schema, meriting a baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'List all FCC Part 15.205 restricted frequency bands' with a specific verb and resource. However, it does not differentiate from the sibling tool 'fcc_restricted_bands', causing potential confusion.

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?

No guidance on when to use this tool versus alternatives like 'fcc_restricted_bands'. Use cases and exclusions are absent.

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

Deploy Server

Other Tools