Skip to main content
Glama

Alshhbaa Brassware Store — نحاسيات الشهباء

Search Alshhbaa Brassware Products

search_products
Read-only

Use when a shopper wants to discover luxury brass chandeliers, table lamps, wall sconces, or glass cups by Arabic or English keywords. Returns matching product IDs, SKUs, VAT-inclusive SAR prices, and canonical storefront URLs.

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": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of product suggestions to return (1-20). Defaults to 5.
queryYesSearch query for chandeliers, chandelier accessories, lamps, and wall sconces (e.g. "ثريا", "chandelier").

Output Schema

NameRequiredDescriptionDefault
contentYes
structuredContentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this as a safe read, so the description's remaining burden is smaller. It does add useful domain behavior — bilingual keyword matching and that prices are VAT-inclusive SAR — but says nothing about ranking, empty-result behavior, or whether results are paginated beyond the schema's limit cap. Adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, trigger first, return shape second, with no filler or repetition. Every clause carries information the agent can act on.

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 simple two-parameter lookup with full schema coverage, a readOnly annotation, and an output schema, the description covers purpose, query language, and result semantics. It slightly over-explains return fields already captured by the output schema, and leaves result ordering and no-match behavior unspecified.

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 coverage is 100%, so the baseline is 3; the description earns an extra point by stating that queries work with Arabic or English keywords, which tells the agent it may pass non-Latin terms. It also broadens the searchable catalog (glass cups) slightly beyond what the query parameter's own description enumerates.

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 concrete verb (discover/search) and the exact product domain: luxury brass chandeliers, table lamps, wall sconces, glass cups, searchable in Arabic or English. That is far more specific than the bare name, and the focus on product discovery implicitly separates it from get_product_details. It stops short of explicitly contrasting itself with any sibling, which keeps it at 4.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The opening 'Use when a shopper wants to discover...' is a clear positive trigger that maps directly to the shopper-intent case. There is no guidance on when not to use it or when to prefer list_categories or get_product_details, so routing between siblings still requires inference.

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.