Skip to main content
Glama

TAGLI - Branded Promotional Products

agentic_quote

הפקת הצעת מחיר רשמית, נעולה ושמורה במסד הנתונים עם קישור PDF מאומת (Tier A/B/C, פתוח לכל סוכן ציבורי ללא צורך בהרשמה מוקדמת או פרטי לקוח). תומך במוצר יחיד או בהצעה משולבת מרובת מוצרים (items[]) ומסתנכרן אוטומטית ל-Quote Builder.

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_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoMulti-item lines array for one unified Quote Builder quote + single PDF. Each item: {product_id, quantity, options: {color, branding, sleeve, sizes, variation_id}}
optionsNoProduct 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[])
idempotency_keyNoOptional idempotency key for safe retries
customer_contactNoCustomer contact fields (name, email, phone, company)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the quote is locked/immutable, persisted to the database, produces a verified PDF link, requires no registration, and auto-syncs to Quote Builder. It omits failure modes and whether repeated calls create duplicates beyond the idempotency key hint in the schema.

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 dense sentences, front-loaded with the core action and output, followed by eligibility and mode support. Nearly every clause earns its place, though the parenthetical eligibility stack is somewhat compressed and could be easier to scan.

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?

For a six-parameter, nested-object mutation with no output schema, the description covers the essential behaviors and names the primary return artifact (PDF link). It leaves minor gaps around idempotency behavior and the exact response shape, but an agent has enough to call it correctly.

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 coverage is 100%, so the schema already documents all six parameters including nested items and options. The description adds only the high-level single-vs-multi selection and does not enrich meanings like how customer_contact interacts with the 'no customer details' claim, so baseline 3 applies.

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 names a specific action (producing an official, locked, database-stored quote) and its output artifact (a verified PDF link), plus the single- vs multi-product modes via items[]. It implies differentiation from the estimate sibling through 'official/locked/stored', but never names agentic_estimate, so the boundary is inferred rather than stated.

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 conveys genuine eligibility context (open to any public agent, no prior registration or customer details required) and the single vs multi-item choice. However, it gives no explicit guidance on when to prefer this over agentic_estimate or agentic_order_intent, so selection between siblings is left 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