Skip to main content
Glama
Sign In
EMC Regulations MCP Server

EMC Regulations MCP Server

by RFingAdam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

fcc_part95_limits

Retrieve emission limits for personal radio services including FRS, GMRS, CB, MURS, and LPRS under FCC Part 95.

Instructions

Get FCC Part 95 personal radio service limits (FRS, GMRS, CB, MURS, LPRS).

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_part95_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceNoRadio service type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations provided. Description only states 'Get', implying read-only, but does not disclose any behavioral traits such as rate limits, authentication requirements, or error handling. With no annotations, the description carries full burden and falls short.

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?

Single sentence, front-loaded with verb and resource, no extraneous information. Efficient and to the point.

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

Completeness5/5

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

For a simple retrieval tool with one parameter and no output schema, the description adequately explains what the tool returns (limits for the specified services). No gaps given the low complexity.

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 includes one parameter 'service' with 100% description coverage and an enum. Description reiterates the enumeration values (FRS, GMRS, etc.) but adds no new meaning beyond the schema. Baseline 3 is appropriate.

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 clearly states 'Get FCC Part 95 personal radio service limits', specifying the action (Get), resource (FCC Part 95 limits), and enumerating the covered services (FRS, GMRS, CB, MURS, LPRS). This distinctly differentiates it from sibling tools like fcc_part15_limit or ised_limit.

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?

Description implies use when needing Part 95 limits for the listed services, but provides no explicit guidance on when not to use it or alternatives (e.g., fcc_part15_limit for Part 15). Usage context is implicit.

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