Skip to main content
Glama

Product details and specs

em_product
Read-onlyIdempotent

Fetches one Emalls product's title, category path, lowest and highest shop price, rating, and specifications by product ID, helping read details after a product search.

Instructions

Get one Emalls product: title, category path, lowest and highest shop price, rating and specs.

Use it after em_search to read specs. Shops and prices: em_offers. Unsold products have no prices.

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

Input Schema

NameRequiredDescriptionDefault
product_idYesArgument is `product_id` (not `id`): the `id` of an em_search result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.1
    • changedInput schema / properties / product_id / description
      Previous value: -"Product id from em_search."New value: +"Argument is `product_id` (not `id`): the `id` of an em_search result."
  2. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / product_id / description
      Previous value: -"Emalls product id from em_search, e.g. 26506037."New value: +"Product id from em_search."
  3. First observedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds a genuine edge case beyond them: unsold products carry no prices, which tells the agent how to interpret null/absent price fields rather than treating them as an error.

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, front-loaded with what is returned, followed by a short routing note. Every clause carries either scope, sequencing, or the sibling hand-off; nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 supplies the return fields and the one non-obvious data condition (unsold products have no prices). Nothing further is required for correct invocation.

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% and the schema itself already warns that the argument is `product_id` not `id`. The description reinforces provenance ("after em_search") but adds no new constraint such as valid range, error behavior on unknown ids, or lookup cost. Baseline 3 applies when the schema carries the semantics.

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?

Names a specific verb and resource ("Get one Emalls product") and enumerates the payload the agent receives: title, category path, lowest/highest shop price, rating, specs. It also distinguishes itself from siblings by directing shop-level data to em_offers, so an agent can identify the tool without opening the schema.

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?

Gives an explicit workflow position ("Use it after em_search to read specs") and routes a competing need to em_offers for shops and prices. What is missing is an explicit exclusion in the negative case (e.g. don't use this for listing or searching), but the intended context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.