Skip to main content
Glama
Sign In
EMC Regulations MCP Server

EMC Regulations MCP Server

by RFingAdam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

iso16750_conditions

Select an environmental category and mounting location to obtain ISO 16750 test conditions for automotive electronic equipment, covering electrical, mechanical, climatic, and chemical exposure.

Instructions

Get ISO 16750 environmental conditions for automotive electronic equipment. Covers electrical loads, vibration, temperature, and chemical exposure by mounting location.

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

Input Schema

NameRequiredDescriptionDefault
categoryNoEnvironmental category
locationNoMounting location

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. The verb 'Get' suggests a read-only operation, but this is not explicitly stated, and no details on data format or side effects are given.

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 concise with two sentences, front-loading the action ('Get') and key purpose. No redundant or wasted 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?

The description covers purpose and filtering dimensions but lacks information on output format or prerequisites. Given no output schema, a brief hint on return structure would improve completeness.

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 description coverage is 100%, so baseline is 3. The description adds context (automotive electronic equipment, coverage areas) but does not significantly enhance understanding beyond what the schema's enum descriptions provide.

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 ISO 16750 environmental conditions, specifying covered areas (electrical loads, vibration, etc.) and filtering by mounting location. This distinguishes it from sibling tools focused on EMC or other 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 automotive electronic equipment environmental conditions but lacks explicit guidance on when to use this tool versus alternatives, such as other standards tools among siblings.

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