Skip to main content
Glama

Moqway

Get product details

get_product
Read-onlyIdempotent

Full listing: SKUs with ids and live stock, quantity price tiers (USD per sale unit), MOQ, carton packing (units per carton, size, gross weight), China HS code, battery/liquid/magnet/powder flags, certifications and the supplier's Moqway rating. 'unit' and pieces_per_unit say what one unit is (a piece, or a pack such as 1,000 pcs); quote_order quantities count the same units. Use the sku_id values in quote_order.

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": {
      "product_id": "<product_id>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds concrete return behavior: live stock, USD price tiers per sale unit, MOQ, carton details, HS code, battery/liquid/magnet/powder flags, certifications, supplier rating, and unit semantics. It does not cover not-found/error behavior, but that is a minor gap for a read-only detail tool.

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 dense sentences, front-loaded with 'Full listing'; the field enumeration is compact and the quote_order note is actionable. It is long but not padded, though 'Full listing' is slightly non-standard as an opening verb.

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 one-parameter read tool with no output schema, the description is rich on return fields and unit semantics. However, it omits how to source product_id and does not route the agent to search_products, leaving a key setup step unstated.

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

Parameters1/5

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

Schema coverage is 0% for the single required product_id, and the description never mentions product_id, its format, or where to obtain it. It instead discusses sku_id and units for quote_order, which adds contextual vocabulary but no meaning for the required input parameter.

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 the product-detail resource and enumerates the detailed data returned: SKUs, live stock, quantity price tiers, MOQ, carton packing, HS code, flags, certifications, and supplier rating. It is clear this is a product-detail retrieval, though it does not explicitly contrast with search_products or state that it retrieves by product_id.

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?

It gives a useful downstream instruction that quote_order uses the sku_id values. However, it does not say when to use get_product versus search_products, nor how to obtain the required product_id, so usage is only implied.

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