PT Distinction MCP Server and API by Cotlet

List clients in PT Distinction

pt_distinction_list_clients

Read-onlyIdempotent

List clients in the user's own PT Distinction account from ChatGPT, Claude or any AI agent. Returns how to do it in PT Distinction step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's PT Distinction Cloud Browser. PT Distinction's official API: PT Distinction publishes no public API or developer docs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pt_distinction_list_clients"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, non-destructive, idempotent and closed-world, so the safety profile is covered. The description adds genuinely non-obvious context: the tool 'opens nothing by itself' and returns procedural guidance, plus the fact that PT Distinction has no public API, which explains why a guide tool exists at all.

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?

Three sentences, front-loaded with the scope and the key caveat that nothing is opened. The trailing 'PT Distinction's official API: PT Distinction publishes no public API' is slightly redundant in construction but short enough to justify its place.

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?

With no parameters, no output schema and full annotation coverage, the description needs only to explain what comes back and what to do next, which it does. A minor gap is that it does not state whether a Cloud Browser session must already be open or authenticated before the follow-up browser calls.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline applies. No parameter confusion is possible given the empty schema.

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?

The description names a concrete verb and resource (list clients) scoped to 'the user's own PT Distinction account', then immediately corrects the expectation by saying it returns step-by-step instructions rather than data. The mismatch between the name 'list_clients' and the guide-style behavior is resolved within the description, though the opening sentence alone could mislead an agent skimming it.

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?

It gives an explicit workflow: call this to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the PT Distinction Cloud Browser. It does not name which specific browser tools or note when to prefer a different pt_distinction_* sibling, but the next-step routing is clear.

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

All PT Distinction MCP Server and API by Cotlet 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.

Resources

Need Help?