Skip to main content
Glama

Cena dla ilości

offer-get-product-price
Read-onlyIdempotent

Price from WooCommerce and this product description. 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
product_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, openWorld=true, so the safety profile is covered. The description adds real behavioral context beyond them: ambiguous tiers short-circuit to requires_confirmation with no quote, availability is owner-declared without inventory verification, and checkout discounts are not verified. That is exactly the kind of caveat an agent needs before trusting a returned 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?

Most sentences carry genuine policy weight and the rounding rule is reasonably front-loaded. However the first sentence is garbled and front-loads ambiguity rather than the core action, costing a clear opening hook even though overall length is acceptable.

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

Completeness3/5

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

An output schema exists, so return structure need not be explained, and the description correctly focuses on caveats (owner-declared availability, unverified discounts, net/gross reporting). But for a three-required-parameter tool at 0% schema coverage it leaves the caller guessing how to form quantity and which unit variant applies, and it never says how to obtain product_id despite naming the relevant siblings.

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 parameter meaning and it largely does not: quantity is a string with a comma-or-dot decimal pattern whose format is never explained, and the nine-value unit enum (m2 vs m2_actual vs m2_cover, mb, sheet, pack, roll) has materially different semantics that go undefined. Only a loose link between 'unit'/'billable quantity' and the required inputs is present.

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

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name and the phrase 'Price from WooCommerce and this product description' point at price retrieval, and the body reveals it computes a tiered volume price with a rounding policy. However the opening clause is grammatically unclear and the description never distinguishes this tool from the siblings offer-get-product or offer-search-products, so an agent must infer the boundary.

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

Usage Guidelines2/5

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

It states how to resolve quantity gaps, overlapping boundaries, and 'other ambiguity' (which yields requires_confirmation with no quote), which is useful invocation policy. But there is no explicit guidance on when to call this versus offer-get-product for a single-quantity lookup or offer-search-products for discovery, and no stated prerequisites such as already having a valid product_id.

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