Skip to main content
Glama
Sign In
EMC Regulations MCP Server

EMC Regulations MCP Server

by RFingAdam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

standard_cross_reference

Cross-reference EMC standards across major markets. Input a standard category and optionally a market to get equivalent standards in US, EU, Japan, Korea, and other regions.

Instructions

Find equivalent standards across different markets. E.g., CISPR 32 equivalents: FCC Part 15B (US), ICES-003 (CA), EN 55032 (EU), VCCI (JP), KN 32 (KR).

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": "standard_cross_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoStandard category to cross-reference
marketNoFilter by specific market (us, eu, japan, korea, china, etc.)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.6/5.0
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 behavioral traits such as whether the tool is read-only, requires authentication, or has any side effects. For a lookup tool, the lack of transparency 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 two sentences with an illustrative example. It is concise, front-loaded with the core purpose, and contains no superfluous words.

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 simple nature of the tool (two optional parameters, no output schema), the description is nearly complete. The example demonstrates typical usage and results. Minor improvement could be noting that no output schema exists.

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?

With 100% schema description coverage, the schema already documents both parameters. The description's example adds context but does not enhance parameter meaning beyond the schema. Baseline score 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?

The description clearly states the tool finds equivalent standards across markets, with a concrete example showing mappings like CISPR 32 to FCC Part 15B, etc. This distinguishes it from sibling tools that focus on specific limits or standards.

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 usage for cross-referencing but does not explicitly state when to use this tool versus alternatives like individual limit lookups (e.g., cispr_limit, fcc_part15_limit). No guidance on prerequisites or typical use cases.

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