Name: tps-check
Author: withoneai

Imported from withoneai/one-agent-plugin (platforms/one-tps-check/skills/tps-check/SKILL.md). Install upstream with npx skills add withoneai/one-agent-plugin --skill tps-check. Copyright stays with the author.

name: tps-check description: TPSCheck is a compliance verification service that provides access to UK Telephone Preference Service screening, allowing businesses and developers to check phone numbers against TPS and CTPS registers before making marketing calls. Read and write TPSCheck data through One: batch, status, credits, check and more, 4 actions with real parameter documentation. Use whenever the user asks to look something up in TPSCheck, create or update a record there, or build code against the TPSCheck API. license: One-Knowledge-1.0 (https://www.withone.ai/licenses/knowledge) metadata: author: one-systems attribution: Integration knowledge by One (withone.ai) platform: tps-check generated-from: one-knowledge-base

TPSCheck through One

TPSCheck is a compliance verification service that provides access to UK Telephone Preference Service screening, allowing businesses and developers to check phone numbers against TPS and CTPS registers before making marketing calls.

One exposes TPSCheck through four MCP tools. The table below carries real action ids from One's knowledge base, so for a common operation you can skip search and go straight to reading the action's parameters.

How to run an action

Find the action in the table below, or call search_one_platform_actions with platform tps-check if it is not listed.
Call get_one_action_knowledge with the action id. Do this every time, including for actions in this table. The table gives you the id, not the parameters.
Call execute_one_action with parameters copied from that knowledge.

Never guess a parameter name, a body field, or an enum value. The knowledge has the real schema, and a guessed field is either a 400 or a silent write of the wrong thing.

Before you start

Call list_one_integrations once and confirm TPSCheck is connected. If it is missing, the user has not connected it: say so and point them at https://app.withone.ai rather than reaching for raw HTTP.

Each connection carries an access field. If it reports {"policy": "methods", "methods": ["GET"]} the agent is read-only here, so plan a read-only answer instead of attempting a write that will be refused.

Before a write

Creates, updates, deletes and sends land on a real TPSCheck account and cannot be recalled. State the action and the specific target in one line before the first write in a task, and let the user stop you. Reads need no confirmation.

Actions

Batch

Action	Method	Path	Action id
Batch Endpoint	POST	`/batch`	`conn_mod_def::GLptu9rh8cg::_IzzE1OHQvqtPh9WgORqlA`

Status

Action	Method	Path	Action id
Status	GET	`/status`	`conn_mod_def::GLptu_3ba6A::2RlVhHXFS5Ojvv3sJFgeBg`

Credits

Action	Method	Path	Action id
Get Credits	GET	`/credits`	`conn_mod_def::GLptvC9zPIg::uwGroVU5RdybWWwF-ckyEQ`

Check

Action	Method	Path	Action id
Check	POST	`/check`	`conn_mod_def::GLptvEO1Lhg::0H-OnfTMRLmFle4A3rzAIw`

When a call fails

The error comes from TPSCheck, not from One. A 400 or 422 means your parameters do not match the schema, so re-read the knowledge and fix the field. A 401 or 403 means the connection needs re-authorizing, which no retry will fix. A 404 means the id is not on this account. A 429 means slow down. Never retry a write more than once: the first attempt may have landed.

Full catalog: https://www.withone.ai/knowledge/tps-check

Integration knowledge by One (withone.ai), licensed under One-Knowledge-1.0. Attribution must be preserved in derivative works.

Install tps-check and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "withoneai-one-agent-plugin-tps-check", "kind": "skill", "name": "tps-check", "description": "TPSCheck is a compliance verification service that provides access to UK Telephone Preference Service screening, allowing businesses and developers to check phone numbers against TPS and CTPS registers before making marketing calls.", "publisher": "withoneai", "version": "1.0.0", "capabilities": { "domains": [ "legal" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "TPSCheck is a compliance verification service that provides access to UK Telephone Preference Service screening, allowing businesses and developers to check phone numbers against TPS and CTPS registers before making marketing calls." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/withoneai/one-agent-plugin", "path": "platforms/one-tps-check/skills/tps-check/SKILL.md", "ref": "fea6ed936a964517ca1b97c4342c3855cd031ef8", "url": "https://github.com/withoneai/one-agent-plugin/blob/fea6ed936a964517ca1b97c4342c3855cd031ef8/platforms/one-tps-check/skills/tps-check/SKILL.md", "key": "withoneai/one-agent-plugin/platforms/one-tps-check/skills/tps-check/SKILL.md" } }, "instructions": "---\nname: tps-check\ndescription: TPSCheck is a compliance verification service that provides access to UK Telephone Preference Service screening, allowing businesses and developers to check phone numbers against TPS and CTPS registers before making marketing calls. Read and write TPSCheck data through One: batch, status, credits, check and more, 4 actions with real parameter documentation. Use whenever the user asks to look something up in TPSCheck, create or update a record there, or build code against the TPSCheck API.\nlicense: One-Knowledge-1.0 (https://www.withone.ai/licenses/knowledge)\nme", "cost": { "context_tokens": 929 } }

tps-check

About