Skip to main content
Glama

getecoback-raumklima

tisken_50400307_zwei_wandfelder_oberflaeche

Read-only

Zwei Wandstellen für IKEA TISKEN nach Belag und Fuge einordnen — Screen two locations against IKEA’s documented surface conditions.

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": {
      "artikel_50400307_belegt": "<artikel_50400307_belegt>",
      "a_material": "<a_material>",
      "b_material": "<b_material>",
      "a_fuge": "<a_fuge>",
      "b_fuge": "<b_fuge>",
      "beide_felder_erfasst": "<beide_felder_erfasst>"
    },
    "name": "tisken_50400307_zwei_wandfelder_oberflaeche"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_fugeYesSchneidet eine sichtbare Fuge das tatsächliche Kontaktfeld an A?
b_fugeYesSchneidet eine sichtbare Fuge das tatsächliche Kontaktfeld an B?
a_materialYesGeprüfte Oberfläche von Stelle A.
b_materialYesGeprüfte Oberfläche von Stelle B.
beide_felder_erfasstYesWurde das ganze Kontaktfeld an beiden Stellen angesehen?
artikel_50400307_belegtYesSteht 504.003.07 auf der Verpackung oder dem eindeutig zugeordneten Beleg?

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 establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the evaluation is against 'documented' IKEA surface conditions, implying a rule-based comparison rather than free judgement, but it never says what the classification result looks like or how ambiguous cases are handled.

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?

A single sentence with the key condition front-loaded, and no filler. The German/English duplication is mild redundancy, though it aids accessibility for mixed-language agents.

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 read-only tool with six fully documented required parameters, the definition is usable, but with no output schema the description should at least sketch the verdict returned per location (e.g., approved/rejected per surface and joint). That result-shape gap is the main completeness shortfall.

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 every parameter including the two enum fields is already documented in the schema. The description's phrase 'nach Belag und Fuge' loosely mirrors the material and joint parameters, but it adds no new detail about enum choices or the meaning of the two confirmation flags.

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 names a specific verb ('einordnen' / 'screen') and resource ('Zwei Wandstellen' / two locations) tied to a concrete product, IKEA TISKEN, so an agent can tell this is a surface-suitability classification task. It does not, however, contrast itself with any sibling screening or surface-check tool, leaving differentiation to the product name alone.

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: 'Screen two locations against IKEA's documented surface conditions' suggests a pre-mounting check, but there is no statement of when to call this versus other surface/site tools, and no explicit exclusions or prerequisites. Nothing is misleading, but the agent must infer the situation.

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