tollbooth-authority

authority_mint_coupon

Create a new operator-owned discount coupon.

The coupon owns its binding: tool_ids names the tools it discounts, and re-pricing a tool never touches it. A coupon bound to no tool discounts nothing, however many patrons redeem it.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	The catchy code patrons type to redeem (operator-scoped uniqueness).
`tool_ids`	No	The tools this coupon discounts — tool ids or MCP tool names, or ``["*"]`` for every tool priced above zero.
`dpop_token`	No
`total_uses`	No	Aggregate cap across all patrons (default None = unlimited).
`valid_from`	Yes	ISO-8601 datetime when the coupon becomes active.
`valid_until`	Yes	ISO-8601 datetime when the coupon expires.
`uses_per_patron`	No	How many tool calls one patron can claim the discount on (default 1; pass null/None for unlimited within the window).
`discount_percent`	Yes	Percentage off the base price (0-100).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

addedInput schema / properties / tool_ids

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The tools this coupon discounts — tool ids or MCP\ntool names, or ``[\"*\"]`` for every tool priced above zero."
+}

Changed6 schema fields changedAug 30, 2026

addedInput schema / properties / discount_percent / description
```
Added value: +"Percentage off the base price (0-100)."
```

addedInput schema / properties / name / description

Added value: +"The catchy code patrons type to redeem\n(operator-scoped uniqueness)."

addedInput schema / properties / total_uses / description

Added value: +"Aggregate cap across all patrons (default None =\nunlimited)."

addedInput schema / properties / uses_per_patron / description

Added value: +"How many tool calls one patron can claim the\ndiscount on (default 1; pass null/None for unlimited\nwithin the window)."

addedInput schema / properties / valid_from / description

Added value: +"ISO-8601 datetime when the coupon becomes active."

addedInput schema / properties / valid_until / description

Added value: +"ISO-8601 datetime when the coupon expires."

First observedJul 16, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real semantics: the coupon owns its binding, re-pricing a tool does not affect it, and a coupon bound to no tool discounts nothing. That is useful beyond the schema, but it omits permission/auth requirements, idempotency, and any concurrency or rate-limit behavior expected of a minting mutation.

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?

Front-loaded with the action, then two short sentences explaining the binding model. Efficient overall, though the clause 'however many patrons redeem it' is slightly oblique rather than wasteful.

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 values need not be described, and the schema covers parameters well. However, for an unannotated mutation tool, the description never addresses authorization or operator-scoping prerequisites, leaving a gap an agent must guess at.

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 description coverage is 88%, so the schema already documents every field including the tool_ids default of null. The description only reinforces the meaning of an empty tool_ids binding, adding marginal value; baseline 3 is appropriate.

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 precise verb and resource with scope: 'Create a new operator-owned discount coupon.' The verb 'create' cleanly separates it from the coupon siblings that delete, update, forget, list, or redeem, so no sibling schema needs to be opened.

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?

There is no when-to-use or when-not-to-use guidance and no alternative tool is named. An agent is not told how this differs from authority_update_coupon or authority_redeem_coupon in terms of workflow, nor whether prerequisites (registration, operator status) must be met first.

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

All tollbooth-authority tools Inspect

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.