Skip to main content
Glama
Sign In
paperclip-mcp

paperclip-mcp

by shanewiseman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List tool gateway audit events

pc_get_tool_gateway_audit
Read-onlyIdempotent

List tool gateway audit events filtered by app, agent, time window, outcome, and more. Paginated results help monitor gateway access and activities.

Instructions

List tool gateway audit events

Paperclip operation: GET /api/tool-gateway/audit. Authorization class: board_or_agent.

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": "pc_get_tool_gateway_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo

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
Behavior3/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds authorization class (board_or_agent) and the endpoint path, but lacks details like pagination handling or scope of results.

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

Conciseness5/5

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

Extremely concise at two sentences, no filler. The title is repeated but appropriate for a short description. Structure is clean.

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?

Output schema exists, so return values are covered. However, the description fails to explain how to use filters (app, agent, limit, etc.) or note that it is a paginated list. Critical context missing for a list-with-filters tool.

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?

Input schema has 1 nested parameter object with 8 sub-properties, none required, and 0% schema description coverage. The description does not explain any parameter, leaving the agent to infer from property names 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 title and description clearly state the action (list) and resource (tool gateway audit events), and the operation path and auth class are provided. It is easily distinguishable from sibling tools, which cover different resources.

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. No context about filtering, pagination, or scenarios where this tool is appropriate.

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