Skip to main content
Glama

Find the same product under another model number

find_same_product
Read-onlyIdempotent

Finds other model numbers a verified product is sold under (same specs, different region, retailer or color), with the source for each model number.

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": "<product>"
    },
    "name": "find_same_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of text fields (notes, labels, answers). One of: "en" (English), "zh-hant" (Traditional Chinese), "zh-hans" (Simplified Chinese). Default "en". Spec values and model numbers are the same in every language. Example: "zh-hant".en
productYesRequired. The product to look up: slug, model number, another model number, or words from its name (1 to 120 characters, case ignored). Example: "35527" or "PB771".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Language for text fields: en, zh-hant (Traditional Chinese) or zh-hans (Simplified Chinese)."New value: +"Language of text fields (notes, labels, answers). One of: \"en\" (English), \"zh-hant\" (Traditional Chinese), \"zh-hans\" (Simplified Chinese). Default \"en\". Spec values and model numbers are the same in every language. Example: \"zh-hant\"."
    • changedInput schema / properties / product / description
      Previous value: -"Slug, model number or name, for example \"35527\" or \"PB771\"."New value: +"Required. The product to look up: slug, model number, another model number, or words from its name (1 to 120 characters, case ignored). Example: \"35527\" or \"PB771\"."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered by structured data. The description adds real behavioral value by disclosing the shape of the result — model numbers plus the source for each — and by defining which variants count as 'the same'. It does not say what happens when no matches exist or how many results are returned.

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?

A single dense sentence with no wasted words, and the key concept (what 'same product' means) is front-loaded in the parenthetical. It is slightly clause-heavy, but every clause carries information.

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 read-only lookup with no output schema, the description covers purpose, result content, and the definition of a match, which is enough to invoke it correctly. The only gap is edge-case behavior such as zero results or result limits, which is minor here.

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 both the product input (slug, model number, name words) and the lang enum are fully documented in the schema. The description adds only the qualifier 'verified product', implying the lookup expects a known/existing product rather than free text, which is a small but real addition. Baseline 3 applies when the schema carries the parameter burden.

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?

States a specific verb (finds) and resource (other model numbers a verified product is sold under), and unpacks what 'same product' means via the parenthetical (same specs, different region, retailer or color). An agent immediately knows this is an alias/variant lookup rather than a generic product fetch, distinguishing it from get_product or search_products.

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 phrase 'a verified product' suggests you should already have a confirmed product in hand before calling, which nudges toward using this after get_product or search_products. However, there is no explicit when-to-use vs when-not, and no alternative (e.g. compare_products) is named for the case where the agent wants spec differences.

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