Skip to main content
Glama
Sign In
EMC Regulations MCP Server

EMC Regulations MCP Server

by RFingAdam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cispr12_limit

Check CISPR 12 vehicle emission limits at a given frequency to ensure type approval compliance.

Instructions

Get CISPR 12 vehicle-level emission limits for type approval.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "frequency_mhz": "<frequency_mhz>"
    },
    "name": "cispr12_limit"
  }
}

Input Schema

NameRequiredDescriptionDefault
frequency_mhzYesFrequency in MHz

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description is the sole source of behavioral info. It does not mention read-only status, side effects, authentication needs, or return format, leaving the agent uninformed about critical behavioral traits.

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, front-loaded sentence with no wasted words, efficiently conveying the tool's purpose.

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?

For a simple lookup tool with one parameter and no output schema, the description is minimally complete. However, it could benefit from mentioning typical frequency range or output structure, especially given the tool's role in a set of related standards.

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 the parameter 'frequency_mhz' described as 'Frequency in MHz'. The tool description adds no additional semantics to this parameter, so 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?

The description clearly states the tool retrieves CISPR 12 vehicle-level emission limits for type approval, using a specific verb ('Get') and resource, distinguishing it from siblings like cispr25_limit and cispr_limit which target different standards.

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 alternatives, such as cispr25_limit for component-level limits or other emission limit tools. No context or prerequisites are given.

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