Skip to main content
Glama

Get one product

get_product
Read-onlyIdempotent

Returns the full verified spec record for one product, looked up by slug, model number, other model number or name, with its source URL and check date. Recalled power banks are returned with their recall notice.

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": "get_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: its slug, model number, another model number it is sold under, or words from its name (1 to 120 characters, case ignored). If more than one product matches, the error lists the candidates. Example: "A2687", "anker-prime-160w" or "Anker Prime 160W".
categoryNoOptional. Limits the lookup to one category, for when a model number or name matches products in more than one. One of: "chargers", "power-banks", "usb-c-cables", "mini-pcs", "kvm-switches", "usb-c-docks", "ssds", "nas", "wireless-chargers", "monitors", "memory", "power-supplies", "cpu-coolers", "graphics-cards", "video-cables", "ethernet-cables", "pc-power-cables", "usb-cables". No default (all categories). Example: "chargers".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Narrows the lookup when a model number exists in more than one category."New value: +"Optional. Limits the lookup to one category, for when a model number or name matches products in more than one. One of: \"chargers\", \"power-banks\", \"usb-c-cables\", \"mini-pcs\", \"kvm-switches\", \"usb-c-docks\", \"ssds\", \"nas\", \"wireless-chargers\", \"monitors\", \"memory\", \"power-supplies\", \"cpu-coolers\", \"graphics-cards\", \"video-cables\", \"ethernet-cables\", \"pc-power-cables\", \"usb-cables\". No default (all categories). Example: \"chargers\"."
    • 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 product name, for example \"A2687\" or \"anker-prime-charger-160w\"."New value: +"Required. The product to look up: its slug, model number, another model number it is sold under, or words from its name (1 to 120 characters, case ignored). If more than one product matches, the error lists the candidates. Example: \"A2687\", \"anker-prime-160w\" or \"Anker Prime 160W\"."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuine context beyond that: results carry a source URL and check date, and recalled power banks include their recall notice, which tells the agent the data is provenance-tagged. It stops short of describing result size, pagination, or what 'verified' means operationally.

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, no filler, with the core return content front-loaded. The recall-notice clause is a deliberate edge-case caveat rather than padding.

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?

With no output schema, the description carries the burden of conveying return content and does so at a useful level: full spec record, source URL, check date, and recall notices. It is adequate for a three-parameter read tool, though it could say more about what fields a spec record contains or how it behaves on no-match.

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 description coverage is 100%, with detailed per-parameter descriptions including examples and the multi-match error behavior, so the schema does the heavy lifting. The description restates the accepted lookup key types but adds no new semantics such as precedence between slug and model number when both could match.

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 specific verb and resource ('Returns the full verified spec record for one product') and enumerates the accepted lookup keys, so the agent knows exactly what the tool does. It does not distinguish itself from siblings such as find_same_product or search_products, leaving that differentiation to the names alone.

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 only implied: the phrase 'for one product' and the list of identifiers suggest this is the single-record lookup to use when an exact slug/model/name is known. There is no explicit statement of when to prefer search_products or find_same_product instead, nor any precondition guidance.

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