Skip to main content
Glama

getecoback-raumklima

gepaarte_stromversuche_richtungsspanne

Read-only

Häufigkeit eines Vorteils in unabhängigen A/B-Paaren mit Unsicherheit angeben — Estimate an uncertainty interval for how often a setting wins in paired repeats.

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": {
      "a_sparsamer": "<a_sparsamer>",
      "b_sparsamer": "<b_sparsamer>",
      "unklar_oder_gleich": "<unklar_oder_gleich>"
    },
    "name": "gepaarte_stromversuche_richtungsspanne"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_sparsamerYesZahl unabhängiger, vergleichbarer Paare, in denen A klar weniger verbrauchte.
b_sparsamerYesZahl unabhängiger, vergleichbarer Paare, in denen B klar weniger verbrauchte.
unklar_oder_gleichYesPaare ohne klare Richtung unter Berücksichtigung des eigenen Messspielraums.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the result is an uncertainty interval and that pairs must be independent, which is useful behavioral context. It does not discuss assumptions such as comparable pairs or how ambiguous pairs are handled beyond the schema wording.

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 definition is a single bilingual sentence with the German purpose front-loaded and an English clarification after the dash. There is no redundant or filler wording, and the key concept, an uncertainty interval for paired A/B win frequency, appears immediately.

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 tool is a simple three-parameter statistical calculation with full schema coverage and no output schema. The description states the purpose, the interval concept, and the paired-repeat setting, which is enough for an agent to call it correctly. Additional detail about assumptions or output format would improve completeness but is not strictly required.

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 the schema already defines each of the three counts in detail. The description does not add syntax, constraints, or interpretation beyond what the parameter descriptions provide. A baseline score of 3 is appropriate when the schema carries the parameter semantics.

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 statistical purpose: estimating an uncertainty interval for how often a setting wins in paired A/B repeats. The bilingual phrasing makes the verb and resource clear. It does not explicitly differentiate from sibling tools, though none of the named siblings appear to be direct alternatives.

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?

Usage is implied by the phrase 'in independent A/B pairs' and 'paired repeats', so an agent can infer the context. However, there is no explicit when-to-use guidance, no exclusions, and no named alternative tools. The definition relies on the schema and context to signal applicability.

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