Skip to main content
Glama
Sign In

pricing

by com.tabzoola
OverviewDiscussionsAdmin

Draft a custom tab order (nothing purchased)

draft_order
Read-onlyIdempotent

Use this when the user has their actual list of tab titles (section names, in order) and wants an order drafted: returns the exact price for that build plus an orderUrl that opens Tabzoola's designer with every title pre-filled, for a human to review and complete at checkout. Purchases nothing, reserves nothing, takes no payment; a free PDF proof is emailed before anything prints. Minimum 25 sets, 1-150 titles. Do not use for reverse-printed tabs, PMS ink or custom sheet sizes (quote only) or for anything other than custom-printed tab dividers.

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": "<product>",
      "sets": "<sets>",
      "titles": "<titles>"
    },
    "name": "draft_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
setsYesNumber of sets (minimum 25).
titlesYesTab titles in tab order, one per tab (1-150). The title count sets tabs-per-set.
optionsNoOptional map of optionKey -> choiceId (see get_pricing_capabilities). Omitted options use defaults.
productYesThe product key: "paper" (the only product).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / product / description
      Previous value: -"The product key: \"paper\" or \"poly\"."New value: +"The product key: \"paper\" (the only product)."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the actual side effects: nothing is purchased, reserved, or charged; a free PDF proof is emailed first; and it returns price plus orderUrl for human review at checkout. This is exactly the context an agent needs before calling a draft tool whose name could otherwise suggest a real transaction.

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 text is front-loaded with the when-to-use condition, then the return behavior, then the constraints and exclusions, which is the right order. It is dense but nearly every clause carries either a trigger, an output fact, or an exclusion; only the repeated 'purchases nothing, reserves nothing, takes no payment' triad is slightly redundant.

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?

With no output schema, the description still explains what comes back (exact price, orderUrl, emailed PDF proof) and the human-in-the-loop checkout step. Combined with the annotations and full schema coverage, an agent has enough to select and call the tool correctly without further inference.

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 coverage is 100%, so the baseline is 3, but the description adds meaningful semantics the schema does not: 'Minimum 25 sets, 1-150 titles' restated as hard constraints and the implication that the title list drives tabs-per-set. The optional options map is referenced via get_pricing_capabilities and defaults, tying nested-object behavior to the sibling tool.

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?

The description names a specific action and resource ('draft an order' from a list of tab titles) and states exactly what the tool produces: the exact price plus an orderUrl that pre-fills the designer. It also distinguishes the tool from quoting paths by explicitly excluding reverse-printed tabs, PMS ink, and custom sheet sizes, so an agent can separate it from quote_price.

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?

Usage is triggered precisely ('when the user has their actual list of tab titles... and wants an order drafted') and complemented by clear exclusions pointing at a quote path. The alternative tool is implied via '(quote only)' rather than named as quote_price, so the routing is clear but not fully explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All pricing toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources