Skip to main content
Glama

Is this a good price?

passt_price_insight
Read-only

Read derived price facts for a UCP product. Pass its prod__ id from passt_search. Prices are integer minor units in the current currency; null means unknown or outside safe JSON integers. Change-only observations define price segments clipped to each window; 30/90-day lows and highs include the price already in effect, and typical means within 5% of the time-weighted 30-day median. priceDropPercent is signed (negative means above that median), or null with insufficient history. Seven priced days are required; an unchanged price is typical, and a 90-day low must be strictly below every earlier price segment in that window. trackedSince is the first retained observation; priceStableSince starts the current price segment. observationCount counts retained comparable price changes; priceChanges90d counts those in 90 days. No checkout or purchase; observed catalog prices do not guarantee the store's final price.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/non-destructive annotations, the description discloses substantial behavior: integer minor units, null semantics, segment clipping, 30/90-day window rules, signed priceDropPercent, the seven-priced-day requirement, and what trackedSince and priceStableSince mean. It also states an important limitation: observed catalog prices do not guarantee the store's final price.

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 purpose is front-loaded, and nearly every sentence carries relevant semantic detail because there is no output schema. However, the description is a dense wall of run-on clauses covering many field definitions, making it harder to scan than a structured list would be.

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 complex derived-price tool with no output schema, the description supplies the key field semantics, calculation windows, null behavior, and caveats an agent needs. It is not fully exhaustive about the returned object shape, but it is substantially complete given the supplied annotations.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate for the single id parameter. It does so by explaining that the id should be the prod_<host>_<ref> value obtained from passt_search, which adds meaningful provenance and format guidance beyond the JSON pattern. It still does not fully explain the host/ref components.

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 states a specific verb and resource: 'Read derived price facts for a UCP product.' It also clarifies that the id comes from passt_search, which helps distinguish its role from search. It does not explicitly differentiate itself from the similarly named genesispay_catalog_price_insight sibling.

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 by 'Read derived price facts' and by the instruction to pass a prod id from passt_search. The description also warns 'No checkout or purchase,' which is useful context. However, it does not explicitly say when to choose this tool over passt_product or genesispay_catalog_price_insight.

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