Skip to main content
Glama
RFingAdam

EMC Regulations MCP Server

by RFingAdam

automotive_emc_overview

Retrieve an overview of automotive EMC standards including CISPR 12, CISPR 25, ISO 11452, ISO 7637, and UNECE R10 for vehicle compliance.

Instructions

Get an overview of automotive EMC standards (CISPR 12, CISPR 25, ISO 11452, ISO 7637, UNECE R10).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function `_overview()` that executes the 'automotive_emc_overview' tool logic. It formats an overview of automotive EMC standards (CISPR 12, CISPR 25, ISO 11452, ISO 7637, UNECE R10) using data from AUTOMOTIVE_EMC and CISPR25_LIMITS JSON dictionaries.
    def _overview(self) -> list[TextContent]:
        result = "Automotive EMC Standards Overview\n" + "=" * 50 + "\n\n"
    
        comparison = AUTOMOTIVE_EMC.get("comparison_chart", {})
        result += "## Standards Summary:\n"
        for std in comparison.get("standards", []):
            result += f"  {std['standard']:12} | {std['scope']:35} | {std['type']}\n"
    
        result += "\n## CISPR 25 Classes (Component Emissions):\n"
        classes = CISPR25_LIMITS.get("classes", {})
        for i in range(1, 6):
            result += f"  Class {i}: {classes.get(f'class_{i}', 'Unknown')}\n"
    
        result += "\n## ISO 11452-2 Levels (Component Immunity):\n"
        for level in AUTOMOTIVE_EMC.get("iso_11452_2", {}).get("test_levels", {}).get("levels", [])[:4]:
            result += f"  Level {level['level']}: {level['field_strength_v_m']} V/m\n"
    
        result += "\n## Typical OEM Requirements:\n"
        for req in CISPR25_LIMITS.get("oem_requirements", {}).get("examples", [])[:5]:
            result += f"  {req['component']:25} \u2192 Class {req['typical_class']}\n"
    
        return [TextContent(type="text", text=result)]
  • The tool schema/definition for 'automotive_emc_overview' registered in list_tools(). Name, description and inputSchema (empty object — no parameters required).
    Tool(
        name="automotive_emc_overview",
        description="Get an overview of automotive EMC standards (CISPR 12, CISPR 25, ISO 11452, ISO 7637, UNECE R10).",
        inputSchema={"type": "object", "properties": {}},
    ),
  • The call_tool dispatcher routing 'automotive_emc_overview' to `self._overview()`. This is where the tool name is matched to the handler at runtime.
    elif name == "automotive_emc_overview":
        return self._overview()
  • Data loaded from JSON files that back the overview handler: AUTOMOTIVE_EMC (cispr_12, iso_11452_2, iso_7637_2, comparison_chart) and CISPR25_LIMITS (classes, oem_requirements).
    AUTOMOTIVE_EMC = load_json("automotive_emc.json")
    AUTO_EXTENDED = load_json("automotive_emc_extended.json")
    OEM_SPECS = load_json("automotive_oem_specs.json")
    ISO16750 = load_json("iso16750_environmental.json")
Behavior3/5

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

No annotations are present, so the description carries full burden. It declares a read operation ('Get an overview') with no side effects or additional behavioral traits disclosed. This is neutral but adequate.

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?

A single, front-loaded sentence with no redundancy. Every word serves a purpose.

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 absence of parameters and output schema, the description sufficiently conveys the tool's scope. It could optionally mention return format, but is complete enough for an overview tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters, schema coverage is 100% and baseline is 4. The description adds value by listing covered standards, providing context beyond the empty 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?

The description clearly states the tool provides an overview of specific automotive EMC standards, using verb 'Get an overview' and listing concrete standards (CISPR 12, CISPR 25, etc.). This distinguishes it from sibling tools that focus on individual limits or methods.

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 a high-level overview but does not explicitly state when to use this tool vs. alternatives like cispr12_limit. No when-not-to-use guidance is provided.

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