Skip to main content
Glama

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

Ohmsches Gesetz Rechner online berechnen

bot_009
Read-onlyIdempotent

[Markt: CH/DE | Norm: Fachformel ohne Normbezug] Ohmsches Gesetz Rechner online berechnen: berechnet Strom I [A]; Leistung P [W]. WANN VERWENDEN: Wenn Strom I für diese Aufgabe orientierend bestimmt oder ein Angebot beziehungsweise eine Auslegung plausibilisiert werden soll. EINGABEN: Spannung U [V] (0.1–1000); Widerstand R [Ohm] (0.1–100000). 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_009"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoDE = Deutschland/Österreich (DIN VDE, eBay.de), CH = Schweiz (NIN/SIA, eBay.ch)DE
spannung_uNoSpannung U [V], 0.1–1000
widerstand_rNoWiderstand R [Ohm], 0.1–100000

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered structurally. The description adds real context beyond that: results are non-binding preliminary sizing, valid only inside the stated input range, and carry no norm acceptance or price/availability claims. Return format is not described, but only 'I' and 'P' are claimed, which is minor.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The labelled blocks (Markt/Norm, WANN VERWENDEN, EINGABEN, GRENZEN) are front-loaded and easy to scan, with no filler sentences. The only redundancy is the opening phrase restating the tool title almost verbatim.

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 simple two-input calculator with no output schema, the description supplies what the schema cannot: that 'I' and 'P' are returned, that results are indicative only, and the scope limits. The unmentioned region parameter is a small gap, but the field's own enum description covers it.

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 the schema already documents U and R including units and bounds, and the description merely repeats those exact ranges (0.1–1000, 0.1–100000). The 'region' parameter (DE/CH) is only hinted at via the 'Markt: CH/DE' tag rather than explained in the description. Baseline 3 is appropriate when structured fields do the heavy lifting.

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 names a specific tool domain and states concrete outputs: 'berechnet Strom I [A]; Leistung P [W]'. That is a clear verb+resource with the computed quantities spelled out, so an agent knows exactly what comes back. It never differentiates itself from the many numeric sibling tools (bot_010, bot_011, ...), so it falls short of a 5.

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?

An explicit 'WANN VERWENDEN' block states the situation to use it in: orienting determination of current I, or plausibilizing an offer/design. The 'GRENZEN' block also excludes execution planning, norm acceptance, and pricing/availability. It stops short of naming an alternative tool for those excluded cases.

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