Skip to main content
Glama
Sign In
slidecold-mcp

slidecold-mcp

by slidecold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Retry failed recipients

retry_campaign

Resets failed recipients in a campaign to pending and retries delivery, returning completed campaigns to active when retries are queued.

Instructions

Retry failed recipients. Required API key scope: campaigns:write. POST /campaigns/{id}/retry Resets FAILED recipients to PENDING. A COMPLETED campaign with at least one retried recipient is set back to ACTIVE.

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": {
      "id": "<id>"
    },
    "name": "retry_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter `id`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare the mutating, non-idempotent, non-destructive profile, and the description adds real context beyond them: the required campaigns:write scope and the side effect that a COMPLETED campaign is flipped back to ACTIVE. The one significant gap is whether the retry immediately enqueues sending or only resets state for a later start.

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?

Four short lines, front-loaded with the action, then auth scope, then endpoint, then the state-machine consequence. Every line earns its place and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation with no output schema, the definition covers the auth requirement and the observable state effects, which is most of what an agent needs. It does not say what the call returns or whether repeated calls on an already-reset campaign are safe, despite idempotentHint=false.

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 100%, but the schema text for `id` is only 'Path parameter `id`.' The description compensates slightly by showing the path template /campaigns/{id}/retry, clarifying that the id is a campaign id rather than a recipient id. That is a modest gain over a trivially documented schema, consistent with the baseline 3.

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 states a specific verb+resource ('Retry failed recipients') and pins it to a concrete operation, POST /campaigns/{id}/retry, which no sibling tool offers. It is unambiguous what the tool does, though it never names a sibling to contrast against, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the name and the state-change note ('Resets FAILED recipients to PENDING'), which tells the agent the tool presupposes a campaign with failed recipients. There is no explicit when-not guidance, no mention of prerequisites beyond the API scope, and no comparison to update_campaign or get_campaign_stats.

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