Skip to main content
Glama

getecoback-climate-weather

dunstabzug_geruchsprobe_spitze_dauer_entscheidung

Read-only

Erkenne, ob die schwächere Geruchsspitze in der eigenen Nachprobe mit einer längeren Beobachtungszeit einherging — Distinguish odor intensity from persistence in a matched kitchen trial

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": {
      "vor_spitze": "<vor_spitze>",
      "nach_spitze": "<nach_spitze>",
      "vor_dauer_min": "<vor_dauer_min>",
      "nach_dauer_min": "<nach_dauer_min>",
      "gleiche_skala_und_dauer": "<gleiche_skala_und_dauer>"
    },
    "name": "dunstabzug_geruchsprobe_spitze_dauer_entscheidung"
  }
}

Input Schema

NameRequiredDescriptionDefault
vor_spitzeYesEigene höchste beobachtete Einstufung vor Änderung auf der Skala 0 bis 5
nach_spitzeYesEntsprechend höchste beobachtete Einstufung nach Änderung
vor_dauer_minYesMinuten mit belegter Geruchswahrnehmung im ersten vollständigen Fenster
nach_dauer_minYesEntsprechende Minuten in der vollständigen Nachprobe
gleiche_skala_und_dauerYesGleiche Einstufung, Kochaufgabe, Umgebung und vollständige Fensterdauer bestätigt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/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 no behavioral context beyond that. It does not say what the tool returns (a verdict? a comparison? a threshold?), whether the caller must ensure a prior matched trial exists, or what happens if the sample windows are incomparable. For a decision/verdict tool with no output schema, that is a real gap.

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?

It is short (one sentence plus an English gloss) and front-loads the verb 'Erkenne'. However, the German clause is syntactically convoluted and the English gloss ('Distinguish odor intensity from persistence') is a vaguer restatement rather than the operational decision being made, so neither half is maximally efficient.

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?

Five required parameters, no output schema, and no description of the returned verdict, so the definition should explain what the decision produces and under what conditions the comparison is valid. It states the question but not the answer semantics or edge cases (e.g., equal durations, zero peaks), leaving the agent able to call it but not to interpret or verify 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% and each of the five parameters is documented with type, range, and meaning, so the baseline is 3. The description loosely maps 'schwächere Geruchsspitze' to the after-peak value and 'längere Beobachtungszeit' to the after-duration, plus 'matched kitchen trial' to the equality confirmation, but adds no units, thresholds, or interpretation rules beyond the schema.

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 analytical decision: determine whether a weaker odor peak in the follow-up sample coincided with a longer observation window, framed as separating intensity from persistence. That is a concrete verb-plus-resource, not a restatement of the long tool name. It never contrasts itself with any of the many similarly named dunstabzug siblings, so the agent gets no in-description differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no statement of when not to use it, and no named alternative among the many related odor/duration tools. The only usage constraint is implicit in the boolean parameter 'gleiche_skala_und_dauer', which the description never mentions as a precondition.

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