Skip to main content
Glama
Sign In
paperclip-mcp

paperclip-mcp

by shanewiseman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Accept an invite and create or replay a join request

pc_post_invites_by_token_accept

Accept an invitation by token to create or replay a join request, supporting both human and agent types.

Instructions

Accept an invite and create or replay a join request

Paperclip operation: POST /api/invites/{token}/accept. Authorization class: public.

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>",
      "body": "<body>"
    },
    "name": "pc_post_invites_by_token_accept"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
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

C2.8/5.0
Behavior2/5

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

Annotations already indicate mutation (readOnlyHint=false) and non-destructive nature (destructiveHint=false). The description adds no behavioral details beyond stating the operation and auth class. It doesn't mention side effects (e.g., if replays overwrite something), authorization requirements in practice, or rate limits. The contribution over annotations is minimal.

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 very short: one line for purpose, one for operation and auth class. It is front-loaded and efficient. The extra line adds operational context without waste. Could be considered slightly under-specified but not verbose.

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, the description does not mention return values, success/error conditions, or what 'create or replay' means in practice. The tool has nested parameters and multiple fields, but no guidance on their relationships. The openWorldHint suggests extensibility but does not substitute for basic completeness.

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?

With 0% schema description coverage, the description must compensate but provides no information about parameters. The 'path' and 'body' parameters, including 'token', 'requestType', 'agentName', and others, are entirely unexplained. The agent cannot understand what values to supply or their purpose from the description alone.

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 'Accept an invite and create or replay a join request', which is a specific action on a specific resource. The title reinforces this. Among sibling tools, it uniquely handles invite acceptance versus viewing (pc_get_invites_by_token) or revoking (pc_post_invites_by_invite_id_revoke), providing clear differentiation.

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 offers no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., having a valid invite token), when acceptance creates versus replays a request, or when to prefer other invite-related tools. The agent is left to infer usage context.

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