Skip to main content
Glama

Ablakunio Nyílászáró MCP

list_inventory

Read-onlyIdempotent

Listázza az aktuálisan raktáron lévő szabvány nyílászárókat és párkányokat bruttó árral. Lists current ready-stock items with retail prices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description adds that prices are gross/retail and that the scope is ready-stock standard items only, but says nothing about pagination, result size, or whether stock quantities are included (which is what separates it from check_stock).

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, front-loaded with the resource and scope. The English sentence is a near-verbatim translation of the Hungarian one, so half the text is redundant for a single-language reader, but nothing is verbose or buried.

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 no-parameter, read-only tool whose annotations cover the safety profile, this is nearly sufficient. The gap is that there is no output schema, so the agent cannot tell what fields come back (SKU, dimensions, quantity on hand) — and quantity in particular matters given the sibling check_stock.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies no filtering or arguments are required.

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 gives a specific verb and resource ('Lists current ready-stock items') and narrows the inventory to standard windows/doors and sills with retail (gross) prices, so the agent knows exactly what is returned. It does not, however, differentiate itself from the sibling check_stock, which sounds like it queries the same stock data.

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: 'current ready-stock' suggests browsing the whole in-stock catalogue as opposed to checking a single item or requesting a quote. No explicit when-to-use, no prerequisites, and no named alternative (check_stock, get_price_estimate) is mentioned.

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