Skip to main content
Glama
Sign In
paperclip-mcp

paperclip-mcp

by shanewiseman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Revoke a tool gateway session

pc_post_tool_gateway_sessions_by_session_id_revoke
Destructive

Revoke a tool gateway session by session ID to terminate access and invalidate the session.

Instructions

Revoke a tool gateway session

Paperclip operation: POST /api/tool-gateway/sessions/{sessionId}/revoke. Authorization class: board_or_agent.

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_tool_gateway_sessions_by_session_id_revoke"
  }
}

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.4/5.0
Behavior2/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, so the agent already knows this is a destructive operation. The description adds no further behavioral context, e.g., whether revoking disconnects users, triggers side effects, or is irreversible. The 'Authorization class: board_or_agent' hint is present but minimal.

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 very short, but this is not necessarily concise—it lacks important details. The structure is minimal: repeat title, mention HTTP method, path, and auth class. Every sentence earns its place, but more content is needed. Score 3 for being adequate but not wasteful.

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?

Given the tool's complexity (2 params, nested object, output schema exists), the description is incomplete. It does not explain return values, behavior on success/failure, or parameter constraints. The output schema is present but not described. The description leaves too many gaps for an agent to invoke correctly.

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% (no parameter descriptions in schema). The description does not explain the purpose of 'companyId' in body or 'sessionId' in path. For a tool with two required parameters (one nested), this is insufficient. The agent cannot discern parameter roles or required formats.

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?

Description clearly states the action: 'Revoke a tool gateway session'. The verb 'revoke' and resource 'tool gateway session' are specific. However, it does not differentiate from siblings like post_tool_gateway_gateway_tokens_by_token_id_revoke, which also revokes something. Still clear enough for basic purpose.

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 vs alternatives. There are sibling tools for revoking tokens and managing sessions, but the description gives no context about when to revoke a session vs token, or prerequisites (e.g., session must be active). Only mentions authorization class, which is not usage guidance.

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