Skip to main content
Glama

Price a basket and get the checkout link

build_quote
Read-onlyIdempotent

Price a basket of products for a monthly subscription: line totals, subtotal, VAT and total in ILS. Returns online_checkout_url when the basket can be bought online (one SentinelOne plan plus supported add-ons), otherwise a quote request URL. Does not buy anything. Shows an interactive quote with a checkout button where the host supports MCP Apps.

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": {
      "items": "<items>"
    },
    "name": "build_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesProducts to price.

Output Schema

NameRequiredDescriptionDefault
linesYes
vat_ilsNo
currencyYes
quote_request_urlNo
online_checkout_urlNo
monthly_subtotal_ilsYes
monthly_total_with_vat_ilsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: it never transacts, it may emit either a checkout URL or a quote request URL depending on basket eligibility, and it can render an interactive quote when the host supports MCP Apps.

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?

Four sentences, front-loaded with what is computed and in what currency, followed by return-shape and eligibility caveats. Every sentence carries information; the MCP Apps sentence is niche but earns its place for hosts that support it.

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 return values need not be spelled out, yet the description still surfaces the key branch (checkout URL vs quote request URL) and the eligibility constraint that drives it. The main remaining gap is that it does not say what happens to ineligible line items or how the agent should proceed after receiving a quote request URL.

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?

There is a single parameter with 100% schema coverage, so the schema already documents items, item_id enum and quantity semantics. The description adds only the framing that the basket is priced as a monthly subscription, which is helpful context but not new parameter-level detail.

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 and resource (price a basket of products), names the currency and the computed fields, and distinguishes itself from a quote-request flow by explaining that it returns online_checkout_url only for eligible baskets and otherwise a quote request URL.

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?

It implies the eligibility rule (one SentinelOne plan plus supported add-ons) and the fallback behavior, and 'Does not buy anything' hints that purchasing happens elsewhere. But it never explicitly names request_quote as the alternative or states when an agent should call that instead, leaving routing to inference.

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