Skip to main content
Glama

Qadiva — wholesale glassware (UAE & GCC)

Wholesale glassware with dimensions

list_glassware
Read-onlyIdempotent

List Qadiva's core wholesale glassware for hotels, restaurants, caterers and distributors in the UAE/GCC — goblets, tumblers, highballs, jugs and storage jars — with capacity (ml and oz), height, rim and base diameter, weight, typical use and PDF spec sheet. Optional filters: text, category (Stemware, Tumblers, Serveware), capacity range in ml. No 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_glassware"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
max_mlNo
min_mlNo
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower. The description still adds real value by disclosing the exact return payload (capacity in ml and oz, height, rim/base diameter, weight, typical use, PDF spec sheet) and by explicitly excluding prices, which routes the agent elsewhere for costing. Pagination or result-count limits are not mentioned.

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?

Front-loaded with the resource and its scope, then the filter inventory, then the price exclusion in three words. The opening sentence is dense but every clause (audience, region, vessel types, attributes) contributes to correct selection.

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?

With no output schema, the description responsibly lists what comes back, and all four parameters are accounted for despite zero schema coverage. The main remaining gap is operational: nothing about result volume, pagination, or behavior when filters match nothing.

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?

Schema description coverage is 0%, so the description must carry the parameters, and it largely does: text search, the three category values (Stemware, Tumblers, Serveware), and a capacity range in ml mapping to min_ml/max_ml. It stops short of stating match semantics for the query field or whether the ml bounds are inclusive.

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?

Specific verb ('List') plus a precisely scoped resource ('Qadiva's core wholesale glassware for hotels, restaurants, caterers and distributors in the UAE/GCC') and an enumeration of the returned attributes. The catalog-listing nature is unambiguous, though it never explicitly contrasts itself with get_piece (single-item detail) or request_quote.

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 implied rather than stated: the mention of optional filters signals 'browse/search the catalog', and 'No prices' hints that pricing must be obtained elsewhere. There is no explicit when-to-use or when-not-to-use guidance relative to the siblings.

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