PT Distinction MCP Server and API by Cotlet

Send form in PT Distinction

pt_distinction_send_form

Read-onlyIdempotent

Send form 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_send_form"
  }
}

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?

Adds genuinely useful behavior beyond the annotations: 'opens nothing by itself' tells the agent the tool is a guidance-only, read-safe call, consistent with readOnlyHint=true and destructiveHint=false, and the note that PT Distinction publishes no public API explains why browser tools are required. It does not describe the shape or length of the returned steps, a minor gap.

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 compact sentences, front-loaded with the verb and resource, followed by the returned artifact and the required follow-up tools. The trailing sentence about the absence of an official API is somewhat tangential but justifies the browser-tool workflow.

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?

For a zero-parameter, no-output-schema guidance tool, the description covers what it returns (screens, buttons, fields), what it does not do (no action performed), and what must come next. Only the absence of detail about output format or step-count limits keeps it below full marks.

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 no parameter semantics to document; the baseline applies. The description could have noted that form identity is conveyed downstream via browser tools, but nothing is missing from the schema side.

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?

Names a specific verb and resource ('Send form in the user's own PT Distinction account') and immediately clarifies the actual capability: it returns step-by-step instructions rather than performing the send. This corrects the misleading implication of the tool name, though the opening sentence still reads as an action, which could momentarily mislead an agent scanning names.

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?

Explicitly states the follow-up path: use the returned steps with cotlet_browser_* tools in the user's PT Distinction Cloud Browser. It does not name an alternative for cases where a guide is not needed, and does not say when not to use this tool, but the operational context 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?