Skip to main content
Glama
Sign In

genesispay-catalog

by finance.genesispay
OverviewDiscussionsAdmin

Is this a good price?

genesispay_catalog_price_insight
Read-only

Read derived price facts for a UCP product. Pass its prod__ id from genesispay_catalog_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": "genesispay_catalog_price_insight"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

The annotations already mark this as read-only, open-world, and non-destructive, and the description adds substantial behavioral context beyond them. It explains null handling, price-segment construction, window clipping, the meaning of 30/90-day lows and highs, the 5% typical threshold, signed priceDropPercent, history requirements, observation counts, and the caveat that observed catalog prices do not guarantee the store's final price. That is rich transparency for a derived-data read tool.

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 description is front-loaded with purpose and prerequisite, then moves into detailed metric semantics. However, it is a dense paragraph with many semicolon-separated facts, making it harder to scan than necessary. The information largely earns its place because there is no output schema, but the structure could be clearer.

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

Completeness5/5

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

For a tool with one parameter, no output schema, and complex derived price metrics, the description is complete enough to support correct invocation and interpretation. It covers the id source, null semantics, segment rules, window behavior, metric definitions, history requirements, and the final-price caveat. The annotations handle the safety profile, so the remaining burden is appropriately carried by the description.

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, and it does by explaining that the value is a prod_<host>_<ref> id sourced from genesispay_catalog_search. It does not restate the schema pattern or length constraints, but it adds the essential origin and usage meaning. This is strong but not exhaustive parameter documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 distinguishes the tool from the search sibling by telling the agent to pass the prod_<host>_<ref> id obtained from genesispay_catalog_search. An agent can identify this as the price-analysis tool rather than search, reviews, shops, or recent listings.

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

Usage Guidelines4/5

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

The description gives clear context: use it for a product whose id came from genesispay_catalog_search, and it explicitly notes that it does not perform checkout or purchase. It does not explicitly state when not to use it or name alternatives beyond the search tool as an id source. The guidance is clear but lacks explicit exclusions.

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

All genesispay-catalog toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources