taxsort-mcp

taxsort_update_coupon

Patch a coupon's editable fields.

Pass only the fields you want to change. To set a cap to unlimited (NULL in the schema), pass clear_uses_per_patron=true or clear_total_uses=true. Renaming the code is allowed — existing patron redemption rows survive (they key on coupon id). tool_ids replaces the coupon's binding — tool ids or MCP tool names, ["*"] for every paid tool, [] to unbind it.

RESTRICTED to operator — requires proof.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`tool_ids`	No
`coupon_id`	Yes
`dpop_token`	No
`total_uses`	No
`valid_from`	No
`valid_until`	No
`uses_per_patron`	No
`clear_total_uses`	No
`discount_percent`	No
`clear_uses_per_patron`	No

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
+}

First observedJul 16, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations, so the description carries full burden. It discloses the operator-restriction/auth requirement, the NULL-clear escape hatches, the survival of redemption rows on rename, and the '*' / [] semantics for tool_ids. That's substantive behavioral context. Missing: reversibility, rate limits, response shape (though output schema exists).

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 purpose sentence, then focused paragraphs each earning their place. Slightly dense but well organized. No filler.

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?

Given 11 params at 0% schema coverage, no annotations, and an output schema present, the description covers the tricky parameters well and states the auth restriction. It lacks guidance on the plain fields (name, total_uses, valid_from/until, discount_percent) but their names are fairly self-evident.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate, and it does: it explains the clear_uses_per_patron/clear_total_uses pair (the only way to set NULL), the tool_ids binding semantics including '*' and [], and the rename-tolerance of coupon_id. This is exactly the kind of meaning the schema lacks.

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 clear verb+resource ('Patch a coupon's editable fields') and the patch semantics. Siblings include mint_coupon, delete_coupon, forget_coupon but the description doesn't explicitly differentiate from these; still the purpose is unmistakable.

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?

'Pass only the fields you want to change' implies patch semantics, and the clear_* flags explain a specific usage scenario. But there's no guidance on when to use this vs. mint/delete/forget, nor any prerequisite framing beyond the operator restriction.

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

All taxsort-mcp 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.