Skip to main content
Glama

getecoback-raumklima

stromversuch_wiederholungen_planen

Read-only

Wiederholungen aus beobachteter Streuung und gewünschter Genauigkeit grob planen — Plan independent repeats from pilot variation and a chosen precision target.

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": {
      "pilot_standardabweichung_kwh": "<pilot_standardabweichung_kwh>",
      "ziel_halbbreite_kwh": "<ziel_halbbreite_kwh>",
      "pilot_laeufe": "<pilot_laeufe>"
    },
    "name": "stromversuch_wiederholungen_planen"
  }
}

Input Schema

NameRequiredDescriptionDefault
pilot_laeufeYesAnzahl unabhängiger, vergleichbarer Pilotläufe.
ziel_halbbreite_kwhYesGewünschte halbe Breite eines näherungsweisen 95-%-Intervalls, in kWh.
pilot_standardabweichung_kwhYesStichproben-Standardabweichung unabhängiger Pilotläufe, in kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds only that the planning is 'grob' (rough), without explaining assumptions, return format, or any limitations beyond the schema's mention of an approximate 95% interval.

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?

Two short, front-loaded clauses in German and English with no filler. Every word contributes to stating the purpose and basis for planning.

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 three-parameter, read-only calculation tool with no output schema, the description is adequate but incomplete: it does not state what the result looks like (e.g., a number of repeats or a plan object) or any assumptions such as normality. The schema covers the inputs well, but the description should say more about the output to be fully complete.

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%, and each parameter already documents its meaning, units, and bounds. The description adds no parameter-level detail beyond what the schema provides, so the baseline of 3 applies.

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 states a specific verb and resource: 'Wiederholungen ... grob planen' / 'Plan independent repeats', plus the basis ('beobachteter Streuung und gewünschter Genauigkeit'). This clearly distinguishes planning repeats from the sibling that counts real repeats, but it does not explicitly name or contrast with any sibling tool.

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?

It gives clear context for use: when pilot variation and a chosen precision target are available. However, it provides no explicit exclusions or named alternatives (e.g., when to use the counting sibling instead), so it falls short of a 5.

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