Skip to main content
Glama

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

Get Product Details

get_product_details
Read-only

Use after searching or when you already know a product slug, numeric ID, or name and need full details. Returns the live VAT-inclusive SAR price, stock quantity, SKU, Arabic description, image URLs, and canonical product URL.

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": "get_product_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoNumeric product ID.
nameNoProduct name or search phrase when slug is unknown.
slugNoProduct URL slug (e.g. "chandelier-1").

Output Schema

NameRequiredDescriptionDefault
contentYes
structuredContentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With readOnlyHint already declaring it as a safe read, the description adds useful behavioral context: the returned price is live and VAT-inclusive in SAR, and details include stock quantity, SKU, Arabic description, image URLs, and canonical URL. It does not cover authentication or rate limits, but those are lower-priority gaps for a read-only lookup with an output schema.

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?

The description is two tight sentences, front-loading the usage condition and then listing the key returned details. Every sentence carries useful information without repetition or filler.

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?

The output schema and readOnlyHint mean the description need not explain return structure or safety, and it covers usage and key returns well. However, all three parameters are optional and the description does not state whether at least one identifier is required or how to choose among id, name, and slug when several are provided.

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 coverage is 100%, so the input schema already defines the id, name, and slug parameters. The description names the same identifier types and implies name can act as a search phrase when slug is unknown, but it adds little beyond the schema and does not clarify precedence when multiple optional identifiers are supplied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific retrieval action for a single product and clearly scopes it to full details by slug, numeric ID, or name. It distinguishes this lookup from the search step by saying to use it after searching or when an identifier is already known.

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?

It gives clear usage context: use after searching or when you already know a product slug, numeric ID, or name and need full details. It does not explicitly state when not to use it or name search_products as the alternative, but the search context implies the boundary.

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.