Skip to main content
Glama

TAGLI - Branded Promotional Products

agentic_estimate

הערכת מחיר פומבית ישירות ממחירון WooCommerce בצד השרת (Tier A, POST /tagli/v1/agent/estimate). תומך במוצר יחיד (product_id + quantity) או בהצעה משולבת מרובת מוצרים (items[]).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "agentic_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoMulti-item lines array. Each item: {product_id, quantity, options: {color, branding, sleeve, sizes, variation_id}}
optionsNoOptional product configuration options (color, branding, sleeve, sizes, variation_id)
quantityNoRequested package quantity (for single-item requests; omit when using items[])
product_idNoTAGLI WooCommerce Product ID (for single-item requests; omit when using items[])
customer_contactNoOptional customer contact metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It usefully reveals that pricing originates from the server-side WooCommerce price list (i.e., authoritative, not client-computed) and identifies the underlying endpoint. But it never says whether the call is side-effect free, whether authentication is required, whether the returned price is binding or indicative, or how stale the price list may be.

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?

Two sentences, front-loaded with the core operation and then the two request shapes; nothing is padded or repeated. The parenthetical endpoint/tier notation is extraneous to an agent's decision but is compact and harmless.

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?

For a 5-parameter tool with nested objects and no output schema, the description explains inputs well but says nothing about what comes back — whether it's a single total, a per-item breakdown, currency, or any validity window on the estimate. An agent knows how to call it but not what to expect, and no annotation or output schema fills that gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the description earns credit for stating the mutual exclusivity the schema cannot express — product_id+quantity for single-item requests versus items[] for combined offers. It does not add detail on the options object (color, branding, sleeve, sizes, variation_id) or customer_contact beyond what the schema already says.

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?

States a specific verb and resource: a public price estimate pulled directly from the WooCommerce price list server-side, plus the endpoint. It also spells out the two supported shapes (single product_id+quantity vs. multi-item items[]), which makes the tool's scope unambiguous. It stops short of naming a sibling such as agentic_quote to draw the estimate-vs-quote line.

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 description effectively defines two usage modes (single item vs. combined multi-product offer) and the schema confirms omitting product_id/quantity when using items[]. However, it gives no guidance on when to choose this over agentic_quote or agentic_order_intent, nor any preconditions (products must exist, options must be valid) before calling.

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