Skip to main content
Glama

getecoback-climate-weather

pc_log_betriebsarten_gemischte_fenster_grenze

Read-only

Aus zählbaren PC-Messintervallen isolierte Arbeit, dokumentierten Leerlauf und überlagerte Zeiträume auseinanderhalten — Audit state coverage before comparing idle against active thermal readings.

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": {
      "eintraege_gesamt": "<eintraege_gesamt>",
      "ausschliesslich_arbeit": "<ausschliesslich_arbeit>",
      "ausschliesslich_leerlauf": "<ausschliesslich_leerlauf>",
      "uebergang_gesichert": "<uebergang_gesichert>",
      "minimum_je_zustand": "<minimum_je_zustand>"
    },
    "name": "pc_log_betriebsarten_gemischte_fenster_grenze"
  }
}

Input Schema

NameRequiredDescriptionDefault
eintraege_gesamtYesIntervalle im exportierten Beobachtungsfenster.
minimum_je_zustandYesEigenes vorab gesetztes Minimum auswertbarer Abschnitte für beide Gruppen.
uebergang_gesichertYesWeitere Abschnitte mit erkanntem Wechsel während des Messintervalls.
ausschliesslich_arbeitYesDavon vollständig in bestätigter gleichartiger Arbeit.
ausschliesslich_leerlaufYesDavon andere Zeitabschnitte, vollständig als Leerlauf dokumentiert.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations confirm this is read-only and closed-world, but the description does not explain what the audit actually does with the supplied counts, what result it produces, or how it behaves when coverage is insufficient. The behavioral burden remains largely unmet beyond safety hints in annotations.

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

Conciseness3/5

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

The description is short and front-loads the domain concept, but the long hyphenated sentence is dense and abstract, making the structure less clear than its length suggests.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five required numeric inputs and no output schema, the description should clarify the expected result and failure conditions. It mentions auditing coverage but leaves the returned output and boundary semantics unexplained.

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 explains each parameter. The description's references to isolated work, documented idle, and overlapping periods map conceptually to the inputs but add no syntax, constraints, or interpretation beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a domain operation around PC measurement intervals and separating work, idle, and overlapping periods. However, the verb is abstract ('auseinanderhalten' / audit state coverage) and does not clearly state whether the tool validates counts, computes a boundary, or returns a coverage result.

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?

It gives a timing hint: audit state coverage before comparing idle against active thermal readings. It does not name alternatives or exclusions, so the guidance is implied rather than explicit.

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