Skip to main content
Glama
RFingAdam

EMC Regulations MCP Server

by RFingAdam

iso7637_pulses

Retrieve ISO 7637-2 conducted transient immunity test pulses for automotive components to verify compliance with transient immunity requirements.

Instructions

Get ISO 7637-2 conducted transient immunity test pulses for automotive components.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool 'iso7637_pulses' is registered as part of AutomotiveTools with inputSchema (no required params).
    Tool(
        name="iso7637_pulses",
        description="Get ISO 7637-2 conducted transient immunity test pulses for automotive components.",
        inputSchema={"type": "object", "properties": {}},
    ),
  • call_tool dispatches 'iso7637_pulses' to _iso7637_pulses() method.
    elif name == "iso7637_pulses":
        return self._iso7637_pulses()
  • _iso7637_pulses() is the actual implementation: reads AUTOMOTIVE_EMC JSON data under 'iso_7637_2' and formats pulse details (description, voltage range, rise time) and functional status classes.
    def _iso7637_pulses() -> list[TextContent]:
        result = "ISO 7637-2 Conducted Transient Test Pulses\n" + "=" * 50 + "\n\n"
    
        iso_data = AUTOMOTIVE_EMC.get("iso_7637_2", {})
        result += f"{iso_data.get('title', '')}\n\n"
    
        for pulse in iso_data.get("test_pulses", []):
            result += f"## Pulse {pulse['pulse']}\n"
            result += f"  Description: {pulse['description']}\n"
            if "voltage_range_v" in pulse:
                result += f"  Voltage: {pulse['voltage_range_v'][0]} to {pulse['voltage_range_v'][1]} V\n"
            if "rise_time_us" in pulse:
                result += f"  Rise time: {pulse['rise_time_us']} \u00b5s\n"
            elif "rise_time_ns" in pulse:
                result += f"  Rise time: {pulse['rise_time_ns']} ns\n"
            result += "\n"
    
        result += "## Functional Status Classes:\n"
        for cls in iso_data.get("functional_status", {}).get("classes", []):
            result += f"  Class {cls['class']}: {cls['description']}\n"
    
        return [TextContent(type="text", text=result)]
  • AUTOMOTIVE_EMC = load_json('automotive_emc.json') loads the data used by _iso7637_pulses.
    AUTOMOTIVE_EMC = load_json("automotive_emc.json")
  • inputSchema for iso7637_pulses is an empty object (no parameters required).
    inputSchema={"type": "object", "properties": {}},
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'Get ... pulses', implying a read operation, but does not clarify if it returns a single pulse definition, a list, or any other behavioral characteristics such as side effects or restrictions.

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 sentence of 10 words, directly stating the core action and resource. No extraneous information, perfectly front-loaded, and each word earns its place.

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?

Given no parameters, no output schema, and no annotations, the tool description is the sole source of context. It identifies the standard and domain but lacks detail on output format or how results are structured. For a simple reference tool it is minimally adequate, but could be improved with a hint about the returned data.

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?

The input schema has zero parameters, so schema coverage is 100% by default. The description does not need to add parameter details, and the tool functions as a static lookup. Baseline for zero parameters is 4, and this is appropriate.

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?

The description specifies the tool retrieves data for a particular standard (ISO 7637-2) and test type (conducted transient immunity pulses) for automotive components, clearly distinguishing it from sibling tools like 'iso11452_levels' or 'iec61000_overview'. However, it does not clarify the form of the output (e.g., list, table) beyond 'pulses'.

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?

The description provides no guidance on when to use this tool versus the many sibling tools covering different standards (e.g., ISO 11452, IEC 61000, CISPR). No when-to-use, when-not-to-use, or alternative suggestions are given, leaving the agent to infer usage from the name alone.

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