Skip to main content
Glama

fuel_ecom_price_stock

Extracts live price, currency, stock status, SKU, and discount data from Shopify, WooCommerce, and Schema.org product URLs to support real-time e-commerce price and stock tracking.

Instructions

Extracts live price, currency, in-stock status, SKU, and discount delta for Shopify, WooCommerce, and Schema.org product URLs. Cost: $0.005 USDC via x402.

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": {
      "url": "<url>"
    },
    "name": "fuel_ecom_price_stock"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesProduct URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it discloses two important traits: extraction is "live" (not cached) and each call costs $0.005 USDC via x402, which signals a paid, micropayment-gated operation an agent must budget for. It does not cover failure modes, rate limits, or latency, which keeps it short of a 5.

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 short sentences: capability first, cost second. Every clause carries information (returned fields, supported platforms, price, payment protocol) with no filler or repetition of the tool name.

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 one-parameter tool with no output schema, the description usefully enumerates the returned fields (price, currency, in-stock, SKU, discount delta) and the payment model, which is nearly everything an agent needs to invoke it. The remaining gap is behavior on unsupported or unreachable URLs.

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 coverage is 100% for the single `url` parameter, so the schema already documents it; the description adds only the constraint that it must be a product URL on one of three supported platforms. That is a modest semantic addition beyond "Product URL" and matches the baseline 3 for well-documented schemas.

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?

States a specific verb ("Extracts") and enumerates the exact resources returned: live price, currency, in-stock status, SKU, and discount delta. It also scopes the input domain to Shopify, WooCommerce, and Schema.org product URLs, so an agent can immediately tell this is a product-page price/stock scraper rather than any sibling function.

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?

The platform list (Shopify, WooCommerce, Schema.org) implicitly defines applicability, and the stated cost gives an agent a reason to avoid redundant calls. However, there is no explicit when-to-use/when-not guidance, no mention of what happens with unsupported or non-product URLs, and no routing to alternatives.

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