Skip to main content
Glama
Sign In
paperclip-mcp

paperclip-mcp

by shanewiseman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Finish a cloud upstream connection

pc_post_cloud_upstreams_connect_finish

Finalize a pending cloud upstream connection by providing the authorization code and state returned from the external service.

Instructions

Finish a cloud upstream connection

Paperclip operation: POST /api/cloud-upstreams/connect/finish. 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": {
      "body": "<body>"
    },
    "name": "pc_post_cloud_upstreams_connect_finish"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault
bodyYes
headersYes
encodingYes
status_codeYes
content_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already indicate readOnlyHint=false (write), destructiveHint=false, idempotentHint=false. The description adds only the authorization class, which is not behavioral. It does not disclose side effects, the nature of the operation (e.g., finalizing OAuth flow), or any potential outcomes beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short (two lines) but includes irrelevant technical details ('Paperclip operation: ...') that waste space. It is concise but not optimally structured for an AI agent.

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

Completeness1/5

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

Given the complexity of a multi-step connection flow with OAuth parameters and an output schema, the description is severely lacking. It does not explain the overall process, parameter roles, output, or prerequisites, leaving the agent with insufficient context.

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

Parameters1/5

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

Schema coverage is 0%, so the description must explain parameters. It provides no description for 'pendingConnectionId', 'code', or 'state'. The agent receives no hints about what these mean (e.g., OAuth code and state), making it impossible to use correctly without external knowledge.

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 title and first line clearly state 'Finish a cloud upstream connection', which is a specific verb-resource pair. However, it does not differentiate this tool from sibling tools like pc_post_cloud_upstreams_connect_start, and the additional technical details (Paperclip operation, authorization class) do not aid purpose clarity.

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?

No guidance on when to use this tool versus alternatives. The description does not mention that this is the second step after starting a connection, nor does it indicate prerequisites or context for use.

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