Skip to main content
Glama

https://fachrechner.com/api/v1/mcp

Umrechnung von Ampere in Watt

bot_045
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Umrechnung von Ampere in Watt: berechnet Leistung [W]. WANN VERWENDEN: Wenn Leistung für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Stromstärke [A] (0.1–200); Spannung [V] (50–500). GRENZEN: Unverbindliche Vorbemessung (keine Ausführungsplanung, keine Normabnahme, keine Preise oder Lieferbarkeit; gültig nur im angegebenen Eingabebereich).

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

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
voltage_voltNoSpannung [V], 50–500
current_ampereNoStromstärke [A], 0.1–200

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, so the description correctly spends its words elsewhere: the result is explicitly non-binding preliminary sizing and valid only inside the stated input envelope. That is real added context beyond the annotations. It stops short of stating the formula or the exact returned value shape, which for a calculator with no output schema would have been a useful further disclosure.

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?

Labeled blocks (scope, purpose, WANN VERWENDEN, EINGABEN, GRENZEN) front-load the operation and then the decision criteria. Every sentence carries information; nothing is duplicated padding.

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?

For a three-parameter, all-optional calculator with full schema coverage and annotations covering the safety profile, the description supplies purpose, input envelope and validity limits. The only remaining gap is that no output schema exists and the description never states the precise return form or formula, leaving the agent to infer P = U·I.

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% and the schema already documents the ranges, defaults and the region enum, so the description largely restates them (0.1–200 A, 50–500 V). The one genuine addition is "Fachformel ohne Normbezug", which signals that the market/norm context does not change the arithmetic — though this sits slightly awkwardly next to the region enum's DIN VDE / NIN-SIA framing.

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 names a concrete operation and resource: conversion of current in amperes to power in watts ("berechnet Leistung [W]"), and prefixes the market/norm scope. An agent can tell from the first line exactly what computation is performed, independent of the opaque sibling IDs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"WANN VERWENDEN" gives a positive trigger (orientative power determination, plausibility-checking a quote or design), and "GRENZEN" lists explicit exclusions — no execution planning, no standards sign-off, no prices or availability. It does not name an alternative sibling tool, so the routing guidance is context-only rather than comparative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources