Skip to main content
Glama

Cena dla ilości

offer-get-product-price
Read-onlyIdempotent

Current local WooCommerce catalog price, published descriptions and requested-quantity price validation. Inspect reference timestamp, sales_terms, allowed_units, formats and minimum quantity. If format_required is true, ask for format_id. Never quote indicative_offer as a total or a conditional price without its condition. Quantity gaps or conflicting shared boundaries require confirmation; no tier is inferred. Other ambiguity gives requires_confirmation and price=null for the requested-quantity calculation, while available_data still reports the recorded catalog_price and published text/tiers. You may state the recorded shop price with its actual conditions and source; never multiply or treat it as an unconditional quantity quote. Missing current WooCommerce prices remain null, not zero. Always state net/gross, unit, billable quantity, source and exclusions. Availability comes from local WooCommerce stock status; no stock quantities or external verification. Checkout discount is not verified.

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": {
      "product_id": "<product_id>",
      "quantity": "<quantity>",
      "unit": "<unit>"
    },
    "name": "offer-get-product-price"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYes
quantityYes
format_idNo
product_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior5/5

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

With readOnly/idempotent annotations already covering safety, the description still adds substantial behavioral context: no tier is inferred, ambiguous cases return requires_confirmation with price=null while available_data still reports catalog_price, missing prices stay null rather than zero, availability is limited to local WooCommerce stock status with no quantities, and checkout discounts are unverified. It also warns against treating indicative_offer as a total, which is a real misuse guard.

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 in the first sentence, which is good, but the remainder is a dense block of policy rules of roughly equal weight with no grouping or ordering by importance. Most sentences carry real information, yet the reader must parse a wall of caveats to extract the conditional logic.

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?

An output schema exists, so the description need not define return values, and it instead covers the decision logic an agent needs (confirmation paths, null handling, mandatory citation of net/gross, unit, billable quantity, source and exclusions). The remaining gap is input-side: unit and quantity semantics are never explained.

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 0%, so the description must carry the parameter burden, and it only addresses format_id (conditionally, via format_required) and references quantity obliquely. It never explains the nine-value unit enum (m2 vs m2_actual vs m2_cover is genuinely ambiguous) or the quantity string pattern, leaving three required parameters semantically undocumented.

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 opening clause names a concrete verb+resource (retrieve the current local WooCommerce catalog price) and adds a second function (requested-quantity price validation). It is specific enough to distinguish this from a generic product lookup, but it never mentions the siblings offer-get-product or offer-search-products, so an agent must infer the boundary itself.

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 through conditional branches ('If format_required is true, ask for format_id', 'Quantity gaps or conflicting shared boundaries require confirmation'), which does guide agent behavior at call time. However there is no explicit statement of when to choose this tool over offer-get-product, nor any excluded scenarios, so usage must be inferred.

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