Skip to main content
Glama

getecoback-climate-weather

kontaktgrill_kontaktflaeche_formprobe_stuecke

Read-only

Bei erlaubtem festen Zustand Stücke mit brauchbarer Auflage, Teilauflage und freiem Platz getrennt beobachten — Count observed fit categories on a cold, stationary grill surface.

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": {
      "vorgesehene_stuecke": "<vorgesehene_stuecke>",
      "voll_aufgelegt": "<voll_aufgelegt>",
      "teilweise_aufgelegt": "<teilweise_aufgelegt>"
    },
    "name": "kontaktgrill_kontaktflaeche_formprobe_stuecke"
  }
}

Input Schema

NameRequiredDescriptionDefault
voll_aufgelegtYesDavon Stücke mit der vorgesehenen vollständigen Auflage.
teilweise_aufgelegtYesWeitere Stücke, die nur teilweise auf der nutzbaren Fläche liegen.
vorgesehene_stueckeYesAnzahl gleich geformter Prüfmuster für dieselbe zulässige Aufstellung.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/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 by structured data. The description adds a genuine behavioral constraint — the surface must be cold, stationary and in a permitted fixed state — which tells the agent the measurement context matters. It says nothing about the result shape or how counts are validated against the intended total.

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 definition is short and front-loads the precondition, which is good. The German and English clauses, however, largely restate each other without being identical in meaning ("beobachten" vs "count"), so half the text is redundant while also introducing a slight verb mismatch.

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?

For a three-field, fully documented, read-only counting tool with no output schema, the description supplies the necessary context: what is counted and under what physical preconditions. Only the missing link between the three counts (e.g. that they should reconcile with the intended total) keeps it from being 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 of the three numeric fields is documented in the schema itself. The description's three categories loosely mirror voll_aufgelegt, teilweise_aufgelegt and vorgesehene_stuecke, but adds no interpretation, bounds or relationship between them beyond what the schema already states.

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 English clause states a verb and resource ("Count observed fit categories on a cold, stationary grill surface"), which is enough to recognize a counting/observation tool. However, "fit categories" and the German half ("Stücke mit brauchbarer Auflage, Teilauflage und freiem Platz") are abstract, and nothing distinguishes it from the many other kontaktgrill_* siblings.

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?

"Bei erlaubtem festen Zustand" hints at a precondition (permitted fixed state), but it is neither defined nor actionable. There is no guidance on when to choose this tool over the sibling counting tools, and no statement of what it does not cover.

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