Skip to main content
Glama

Ablakunio Nyílászáró MCP

check_stock

Read-onlyIdempotent

Megnézi, van-e a megadott mérethez közeli RAKTÁRON lévő szabvány nyílászáró (gyorsabb, olcsóbb opció). Checks ready-stock standard windows/doors matching a size.

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": {
      "width_cm": "<width_cm>",
      "height_cm": "<height_cm>"
    },
    "name": "check_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
width_cmYes
height_cmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description's real contribution is that matching is fuzzy on size and restricted to on-hand stock, but it leaves the tolerance undefined and says nothing about what is returned.

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?

Two short sentences with the core concept front-loaded; the bilingual duplication adds length without adding information but does not obscure the meaning.

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?

No output schema exists, yet the description never says whether the result is a boolean availability answer, a list of matching products, or size suggestions — which is exactly what an agent needs to plan the next step. For a stock-availability lookup this is a significant omission.

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?

With 0% schema description coverage the description must carry parameter meaning, and it does partially: it establishes that matching is on type (window/door) and on size being 'close to' the requested value. It never explains the width_cm/height_cm units, bounds, or how much tolerance 'közeli' allows.

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?

States a specific verb and resource: checking for ready-stock ('RAKTÁRON lévő') standard windows/doors whose size is close to the given one, and tags it as the faster/cheaper option. This clearly separates it from quote/pricing siblings, though it never names an alternative explicitly.

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?

The parenthetical '(gyorsabb, olcsóbb opció)' implies the situation to pick this tool — when the user wants a quick, cheap stock item rather than a custom order. There is no explicit when-not guidance or reference to request_quote/get_price_estimate as the fallback path.

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