Swapcard MCP Server

swapcard_delete_event_documents

Delete one or more event documents by ID. Provide the event ID and document IDs to remove them from the event.

Instructions

Delete one or more event documents by their IDs.

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": {
      "eventId": "<eventId>",
      "documentIds": "<documentIds>"
    },
    "name": "swapcard_delete_event_documents"
  }
}

Input Schema

Name	Required	Description	Default
`eventId`	Yes
`documentIds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 21, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral consequences. It only mentions that documents are deleted, without noting irreversibility, partial failure behavior, permissions, or impact on related data.

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?

The description is one short, front-loaded sentence with no filler. Every word adds meaning related to the tool's core action.

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?

With no output schema and no annotations, deleting multiple documents by IDs needs more context about return values, failure semantics, or destructive consequences. The description is too minimal to fully prepare an agent for invocation.

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?

Schema coverage is 0%, so the description must compensate. 'By their IDs' clarifies that documentIds are the identifiers, and 'event documents' implies eventId scopes the operation, but no extra detail on format or relationships is provided.

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 uses a specific action verb 'Delete' with a clear resource 'event documents' and the scope 'by their IDs.' It distinguishes itself from sibling tools like swapcard_delete_event_people and swapcard_delete_exhibitors.

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 gives no guidance on when to choose this tool over alternatives or any prerequisites/exclusions. It only states the action, leaving the agent to infer usage context from siblings.

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

Deploy Server