Skip to main content
Glama
Sign In
slidecold-mcp

slidecold-mcp

by slidecold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get campaign stats

get_campaign_stats
Read-onlyIdempotent

Retrieve campaign statistics, including pending and queued totals plus reply rate, to monitor outreach performance and guide follow-up decisions.

Instructions

Get campaign stats. Required API key scope: campaigns:read. GET /campaigns/{id}/stats totalPending counts PENDING + QUEUED. replyRate is round(replied / (sent + replied) * 100).

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

Input Schema

NameRequiredDescriptionDefault
idYesPath parameter `id`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description earns credit beyond that by disclosing the auth scope requirement and the aggregation semantics: totalPending includes PENDING + QUEUED, and replyRate is round(replied / (sent + replied) * 100), which an agent could not infer from the schema or annotations.

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

Conciseness4/5

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

Four short lines, front-loaded with the purpose, then the auth requirement, then the endpoint, then the metric definitions — no padding. The first line merely restates the title, which is the one redundant element.

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?

With no output schema, the description usefully pre-defines two of the returned metric fields (totalPending, replyRate), which is exactly the kind of return-value context an agent needs here. It stops short of enumerating the full stats payload, but given the tool's simplicity and existing annotations, what is present is close to sufficient.

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 description coverage is 100%, and the single `id` parameter is already documented as a path parameter, so the baseline is 3. The description adds no extra meaning about the id (for example, where to obtain it), only repeating it implicitly through the path template.

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 names a specific verb and resource (get campaign stats) and pins it to the concrete endpoint GET /campaigns/{id}/stats, so the operation is unambiguous. However, it never contrasts itself with the sibling get_campaign, which returns the campaign itself, so an agent must infer the stats-vs-entity distinction on its own.

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?

The only usage context given is the required API key scope (campaigns:read), which is a real prerequisite, but there is no statement of when to call this instead of get_campaign or list_campaigns. Usage is implied by the word 'stats' rather than explained.

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