Skip to main content
Glama

Cena dla ilości

offer-get-product-price
Read-onlyIdempotent

Price from the local approved SteelProfil reference snapshot when configured, otherwise local WooCommerce and descriptions. 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. Owner policy: quantity gaps and overlapping boundaries use the next/higher volume tier (lower price). Other ambiguity gives requires_confirmation with no quote. Always state net/gross, unit, billable quantity, source and exclusions. Full availability is declared by the store owner, without inventory 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

A4.1/5.0
Behavior5/5

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

The description adds extensive behavior beyond annotations: source fallback, reference timestamp inspection, format handling, ambiguity confirmation, owner policy for quantity gaps and overlapping boundaries, required quote fields, unverified availability, and unverified checkout discount. These are material behavioral constraints for an agent and are consistent with the read-only, idempotent, non-destructive annotations.

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 dense but front-loads the pricing source and then layers policy rules. Most sentences carry actionable information, though the number of separate rules makes it slightly less scannable than an ideal structured definition.

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 complex pricing tool with an output schema and read-only annotations, the description covers the critical context: data source, ambiguity handling, owner pricing policy, required quote disclosures, availability caveats, and discount caveats. It is complete enough for an agent to use safely.

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 description coverage is 0%, so the description must compensate. It does add useful meaning for format_id and quantity-tier behavior, and references allowed_units and minimum quantity, but it still does not explain product_id, quantity string format, or the unit enum values, leaving clear parameter-level gaps.

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 identifies a quantity-based product pricing lookup, including the source hierarchy: an approved SteelProfil reference snapshot when configured, otherwise local WooCommerce and descriptions. It is specific enough for selection, though it does not explicitly contrast itself with sibling tools such as offer-get-product or offer-search-products.

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?

It gives clear operating context: inspect reference timestamp, sales_terms, allowed_units, formats, and minimum quantity; ask for format_id when format_required is true; and return requires_confirmation when ambiguity remains. It lacks explicit routing guidance against sibling tools, but the internal when-to-use rules are substantial.

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