Skip to main content
Glama
Sign In

TPSClear

by uk.co.tpsclear
OverviewDiscussionsAdmin

Get a payment link for a prepaid pack

buy_credits

Creates a Stripe Checkout payment link for a prepaid pack on the connected account and returns the URL. Nothing is charged by this tool: a person opens the link and pays by card, and the credits land on the account once paid. Needs a live, self-serve account that names its client business. Prices are in minor units in the response. Packs: pack-1k: TPSClear UK API credits (1,000 checks), £9.00 ex VAT; pack-5k: TPSClear UK API credits (5,000 checks), £24.00 ex VAT; pack-10k: TPSClear UK API credits (10,000 checks), £39.00 ex VAT; pack-50k: TPSClear UK API credits (50,000 checks), £149.00 ex VAT; pack-100k: TPSClear UK API credits (100,000 checks), £199.00 ex VAT; pack-500k: TPSClear UK API credits (500,000 checks), £599.00 ex VAT; pack-1m: TPSClear UK API credits (1,000,000 checks), £799.00 ex VAT; pack-5m: TPSClear UK API credits (5,000,000 checks), £2499.00 ex VAT; au_100: TPSClear Australian DNCR washes (100), A$4.00 ex VAT; au_250: TPSClear Australian DNCR washes (250), A$9.00 ex VAT; au_500: TPSClear Australian DNCR washes (500), A$14.00 ex VAT; au_1000: TPSClear Australian DNCR washes (1,000), A$24.00 ex VAT; au_2500: TPSClear Australian DNCR washes (2,500), A$48.00 ex VAT; au_5000: TPSClear Australian DNCR washes (5,000), A$85.00 ex VAT; au_10000: TPSClear Australian DNCR washes (10,000), A$145.00 ex VAT; au_25000: TPSClear Australian DNCR washes (25,000), A$310.00 ex VAT; au_50000: TPSClear Australian DNCR washes (50,000), A$600.00 ex VAT; au_100000: TPSClear Australian DNCR washes (100,000), A$1170.00 ex VAT; dn_100: TPSClear dead number checks (100), £1.00 ex VAT; dn_250: TPSClear dead number checks (250), £2.50 ex VAT; dn_500: TPSClear dead number checks (500), £5.00 ex VAT.

Input Schema

NameRequiredDescriptionDefault
packYesThe pack id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / pack / enum
      Previous value: -[
-  "pack-1k",
-  "pack-5k",
-  "pack-10k",
-  "pack-50k",
-  "pack-100k",
-  "au_100",
-  "au_250",
-  "au_500",
-  "au_1000",
-  "au_2500",
-  "au_5000",
-  "au_10000",
-  "au_25000",
-  "au_50000",
-  "au_100000",
-  "dn_100",
-  "dn_250",
-  "dn_500"
-]New value: +[
+  "pack-1k",
+  "pack-5k",
+  "pack-10k",
+  "pack-50k",
+  "pack-100k",
+  "pack-500k",
+  "pack-1m",
+  "pack-5m",
+  "au_100",
+  "au_250",
+  "au_500",
+  "au_1000",
+  "au_2500",
+  "au_5000",
+  "au_10000",
+  "au_25000",
+  "au_50000",
+  "au_100000",
+  "dn_100",
+  "dn_250",
+  "dn_500"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / pack / enum
      Previous value: -[
-  "pack-1k",
-  "pack-10k",
-  "pack-50k",
-  "au_100",
-  "au_250",
-  "au_500",
-  "au_1000",
-  "au_2500",
-  "au_5000",
-  "au_10000",
-  "au_25000",
-  "au_50000",
-  "au_100000",
-  "dn_100",
-  "dn_250",
-  "dn_500"
-]New value: +[
+  "pack-1k",
+  "pack-5k",
+  "pack-10k",
+  "pack-50k",
+  "pack-100k",
+  "au_100",
+  "au_250",
+  "au_500",
+  "au_1000",
+  "au_2500",
+  "au_5000",
+  "au_10000",
+  "au_25000",
+  "au_50000",
+  "au_100000",
+  "dn_100",
+  "dn_250",
+  "dn_500"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations mark the tool as non-read-only, open-world and non-idempotent; the description adds real context beyond that by explaining no charge occurs here, a human opens and pays the link, credits post after payment, and the response carries prices in minor units. The account prerequisites are an extra behavioral constraint the annotations do not express.

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 and well ordered: what it does, what it does not do, prerequisites, then the catalogue. The pack list is long and semicolon-dense in a single sentence, which is heavy to parse, but each entry carries distinct commercial information that is not available elsewhere.

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?

Covers return value (URL), the payment flow, account prerequisites and response price units, which is strong given there is no output schema. It does not mention link expiry or that repeated calls create additional links, small but relevant gaps for a non-idempotent payment tool.

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?

The schema fully enumerates the pack ids but only labels them 'The pack id.' The description expands each of the 21 enum values with what it buys (checks, DNCR washes, dead number checks), quantity, currency and price, which is exactly the meaning an agent needs to pick correctly.

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 specific verb and resource: creates a Stripe Checkout payment link for a prepaid pack and returns the URL. It also names the platform (Stripe), the target account, and the concrete outcome (credits land once paid), which no sibling tool does.

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?

Gives clear conditions for use: needs a live, self-serve account that names its client business, and clarifies this tool does not itself charge anyone. It does not explicitly route the agent to siblings (e.g., get_account to check existing balances before buying), so it stops short of naming alternatives.

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

All TPSClear 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