Skip to main content
Glama
Sign In
paperclip-mcp

paperclip-mcp

by shanewiseman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Start OAuth sign-in for a tool connection

pc_post_tools_oauth_by_connection_id_start

Initiates OAuth sign-in for a tool connection, enabling secure authorization for API access.

Instructions

Start OAuth sign-in for a tool connection

Paperclip operation: POST /api/tools/oauth/{connectionId}/start. Authorization class: board.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "pc_post_tools_oauth_by_connection_id_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoOptional JSON compatibility payload. The source OpenAPI operation does not declare a request schema.
pathYes

Output Schema

NameRequiredDescriptionDefault
bodyYes
headersYes
encodingYes
status_codeYes
content_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already indicate this is not read-only, not idempotent, and not destructive. The description adds no additional behavioral context, such as side effects (e.g., redirecting the user) or the fact that OAuth sign-in is an interactive flow.

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?

The description is short (two sentences plus operation line) and front-loaded with the main purpose. It is concise without unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema and two parameters, the description is too minimal for an OAuth start flow. It lacks explanation of the OAuth process, what triggers the sign-in, expected output, and any required user interaction.

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

Parameters3/5

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

The input schema covers both parameters adequately: 'body' has a description, and 'path.connectionId' is a simple string. The description does not add extra meaning beyond the schema, so baseline 3 is appropriate.

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?

The description clearly states the action ('Start OAuth sign-in') and the resource ('tool connection'). It is specific and distinguishable from the many sibling tools, as no other tool has a similar verb-resource combination.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It only mentions the authorization class ('board') but does not explain the context or prerequisites for starting an OAuth sign-in.

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

Deploy Server

Other Tools