Swapcard MCP Server

swapcard_create_webhook

Register a webhook subscription for an event by providing the endpoint, secret, and hooks like PROFILE_CREATE to trigger automated callbacks.

Instructions

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>",
      "endpoint": "<endpoint>",
      "secret": "<secret>",
      "hooks": "<hooks>"
    },
    "name": "swapcard_create_webhook"
  }
}

Input Schema

Name	Required	Description	Default
`hooks`	Yes
`secret`	Yes
`eventId`	Yes
`endpoint`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 21, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It states that it registers a subscription but does not disclose what happens upon registration (e.g., immediate activation, verification of endpoint, potential side effects like sending a test payload). No details about permissions or rate limits are mentioned.

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 a single sentence, which is concise, but it lacks a critical structure: it doesn't front-load any usage context or parameter hints. It is not overlong, but the sentence is too sparse to be fully useful, so it doesn't earn a high score.

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 (4 required parameters, no annotations, no output schema) and the presence of sibling webhook tools, the description is incomplete. It omits information about parameter semantics, return value, and any side effects. It fails to cover the knowledge gap left by the schema and annotations.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate, but it provides no parameter explanations. The schema defines four parameters with types and enums for 'hooks', but the meaning of 'secret', 'eventId', and 'endpoint' is not elaborated. For instance, it doesn't clarify that 'secret' is the signing secret for webhook payloads or that 'endpoint' is the HTTPS URL for delivery.

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 description clearly states the action ('Register a new webhook subscription') and the resource ('an event'). It distinguishes from siblings like swapcard_list_webhooks, swapcard_update_webhook, and swapcard_delete_webhook, though it doesn't explicitly mention these alternatives. The purpose is specific and unambiguous.

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 is provided on when to use this tool versus the sibling webhook tools (list/update/delete). The context of registering a subscription is implied but not explicitly contrasted with updating or listing. Missing information about prerequisites like having an eventId or endpoint readiness.

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

Deploy Server