posokanei-mcp

get_price_history

Retrieve detailed price history for a product by its PosoKanei product ID. Supports filtering by country, price type, and tax inclusion.

Instructions

Get product details including price history when available from PosoKanei.

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": {
      "productId": "<productId>"
    },
    "name": "get_price_history"
  }
}

Input Schema

Name	Required	Description	Default
`countries`	No		GR
`priceType`	No		price
`productId`	Yes	PosoKanei product id.
`includeTax`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jul 30, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It notes price history 'when available,' but omits details on data freshness, rate limits, error handling, or what happens when history is unavailable. This is insufficient.

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?

The description is a single, efficient sentence with no redundancy. While concise, it could be expanded slightly to improve clarity without becoming verbose.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 4 parameters, no output schema, and no annotations, the description is too minimal. It lacks details on return format, error responses, or the conditions under which price history is available, leaving significant gaps.

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

Parameters2/5

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

Schema description coverage is only 25% (only productId described), and the description adds no parameter details. It fails to compensate for the low coverage, leaving the agent without guidance on countries, priceType, or includeTax.

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 clearly states the tool retrieves product details and price history from PosoKanei, which matches the tool's name and distinguishes it from siblings like get_product. However, it could be more precise about focusing on price history rather than general details.

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?

The description provides no guidance on when to use this tool versus alternatives such as get_product, search_products, or compare_competitors. It lacks explicit context for selection.

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

Deploy Server