Skip to main content
Glama
Sign In
Asin MCP Server

Asin MCP Server

by asindotdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get a product and its price history

get_product
Read-only

Retrieve a product’s current state and price history by ID for a selected period, including earlier recorded price reads.

Instructions

Get a product and its price history. The product's latest state and every price read of the period, oldest first. The history covers every read of this ASIN on this marketplace, including those made before you added it, so a product added today can come with months of 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": {
      "id": "<id>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesproduct_id returned when the product was added
daysNoHistory period in days Default: 90.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are ordered 'oldest first,' and the history includes reads made before the product was added, which is a non-obvious data-scope trait that could otherwise surprise an agent. It falls short of 5 because the sentence is cut off and says nothing about volume or limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded and free of filler, which is good. However, the description terminates mid-sentence with an ellipsis ('so a product added today can come with months of prices;…'), leaving a dangling clause that reads as truncated rather than deliberate.

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 two-parameter read tool with full schema coverage and no output schema, the description covers purpose, ordering, and an important data-scope caveat. The truncated ending is the main gap; an agent still knows enough to call it correctly, though it lacks any sense of how much history comes back by default.

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%, so both `id` and `days` are already documented in the schema, establishing a baseline of 3. The description reinforces the temporal scope with 'the period' and 'oldest first,' but adds no format or boundary detail beyond what the schema provides.

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 opens with a specific verb and resource: 'Get a product and its price history,' and elaborates that it returns 'the product's latest state and every price read of the period.' That is clearly distinguishable from write siblings like update_product or delete_product, though it never distinguishes itself from get_asin_history or check_product, which sound closely related.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance. Given siblings such as get_asin_history, check_product, and get_offers, an agent must guess whether this tool or one of those is the right call for a given question. The only implicit signal is that this tool returns current state plus history in one shot.

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

Deploy Server

Other Tools