Skip to main content
Glama

getecoback-climate-weather

umweltaussage_stromanteil_abgrenzen

Read-only

Den Anteil des Verbrauchs bestimmen, für den ein eingegebener Strom-Emissionsfaktor belegt ist — Scope an environmental claim to the documented share of electricity use.

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": {
      "gesamt_kwh": "<gesamt_kwh>",
      "belegt_kwh": "<belegt_kwh>",
      "faktor_kg_kwh": "<faktor_kg_kwh>"
    },
    "name": "umweltaussage_stromanteil_abgrenzen"
  }
}

Input Schema

NameRequiredDescriptionDefault
belegt_kwhYesDavon Verbrauch mit zeitlich und sachlich zugeordnetem Emissionsfaktor.
gesamt_kwhYesGesamtstromverbrauch im betrachteten, identischen Zeitraum.
faktor_kg_kwhYesEingegebener, zu diesem Teil dokumentierter Faktor in kg CO2e pro kWh.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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 safety is covered. The description adds that the operation is a scoping/computation restricted to the *documented* portion rather than total consumption, which is useful, but it does not say what the result looks like (a share, a ratio, a percentage) even though no output schema exists.

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?

Very short and front-loaded, with the core action stated first and the English gloss serving as a compact restatement. The bilingual duplication is slight redundancy but aids disambiguation rather than padding the definition.

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-required-numeric-parameter calculation with no output schema and only lightweight annotations, the description should specify the return form and note obvious guards (e.g. documented consumption not exceeding total consumption, zero-consumption behaviour). Those are missing, leaving a definition that is adequate but not fully self-sufficient.

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 all three parameters are already documented. The description echoes two of them ('eingegebener Strom-Emissionsfaktor', 'Anteil des Verbrauchs') without adding constraints, units, or relationships beyond the schema, so the baseline 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 gives a specific verb ('bestimmen' / 'Scope') and a precise resource: the documented share of electricity consumption covered by a supplied emission factor. It is unambiguous on its own, but it does not name or contrast itself with any sibling 'abgrenzen' tool, so differentiation is left to the name.

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 only implied: the phrase 'Scope an environmental claim' hints at the context (justifying a claim against documented consumption), but there is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool.

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