Skip to main content
Glama

Email List Fatigue Projection

bpj_email_list_fatigue_projection
Read-onlyIdempotent

Project mailable list size and total sends across recurring campaigns assuming constant unsubscribe probability and no new contacts.

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": {
      "subscribers": "<subscribers>",
      "unsub": "<unsub>",
      "rounds": "<rounds>"
    },
    "name": "bpj_email_list_fatigue_projection"
  }
}

Input Schema

NameRequiredDescriptionDefault
unsubYes
roundsYes
subscribersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a safe, idempotent, closed-world read, so the bar is lower. The description adds real modeling context the annotations cannot convey — constant unsubscribe rate and zero new contacts — which tells the agent the projection's boundary conditions; it stops short of describing per-round output structure or units.

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?

A single front-loaded sentence with no filler: the computed outputs come first and the qualifying assumptions follow. Nothing is redundant.

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

Completeness3/5

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

For a three-parameter calculation with no output schema, the description covers the outputs at a high level and states the key assumptions. It leaves open the return shape (per-round vs. aggregate totals) and the compounding behavior of the unsubscribe rate, which an agent would need to interpret results.

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 0%, but each parameter carries a descriptive title ("Unsubscribe share per send (%)", "Consecutive sends", "Current mailable subscribers"). The description reinforces that unsub is a constant per-send rate and that rounds are consecutive, yet it does not clarify whether the percentage is applied compounding or whether results break down by round.

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 uses a specific verb ("Project") with two concrete outputs ("mailable list size and total sends") scoped to "recurring campaigns." It is clear what the tool computes, though it does not explicitly contrast itself with any sibling tool.

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 context is implied rather than stated: the assumptions of "constant unsubscribe probability and no new contacts" tell an agent when the model is valid, but there is no explicit when-to-use/when-not guidance or named alternative for list forecasting.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.