Skip to main content
Glama

Newsletter sponsorship break-even calculator

toolfound_sponsorship_break_even
Read-onlyIdempotent

Estimate the clicks, signups, and customers needed to recover a sponsorship cost from your own funnel assumptions. Returns an evidence-bounded result and the canonical web tool URL.

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": {
      "cost": "<cost>",
      "revenue": "<revenue>",
      "margin": "<margin>",
      "signupRate": "<signupRate>",
      "customerRate": "<customerRate>"
    },
    "name": "toolfound_sponsorship_break_even"
  }
}

Input Schema

NameRequiredDescriptionDefault
costYesPrice of the sponsorship in US dollars as a plain number, for example 500. No currency symbol.
marginYesGross margin on that revenue as a percentage, so 80 means 80 percent (not 0.8).
revenueYesRevenue one new customer brings in during your measurement window, in US dollars as a plain number.
signupRateYesShare of sponsorship clicks that become signups, as a percentage, so 12 means 12 percent.
customerRateYesShare of signups that become paying customers, as a percentage, so 8 means 8 percent.

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
linksYes
errorsNo
summaryYes
sectionsYes
canonical_result_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / cost / description
      Added value: +"Price of the sponsorship in US dollars as a plain number, for example 500. No currency symbol."
    • addedInput schema / properties / customerRate / description
      Added value: +"Share of signups that become paying customers, as a percentage, so 8 means 8 percent."
    • addedInput schema / properties / margin / description
      Added value: +"Gross margin on that revenue as a percentage, so 80 means 80 percent (not 0.8)."
    • addedInput schema / properties / revenue / description
      Added value: +"Revenue one new customer brings in during your measurement window, in US dollars as a plain number."
    • addedInput schema / properties / signupRate / description
      Added value: +"Share of sponsorship clicks that become signups, as a percentage, so 12 means 12 percent."
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds that the result is 'evidence-bounded' and that a canonical web tool URL is returned, but it does not explain the funnel model, whether assumptions are linear or any caveats on how the numbers are derived.

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?

Two sentences with the core purpose front-loaded and no redundant restatement of the title. 'Evidence-bounded result' is slightly vague jargon that costs a little clarity, but nothing is padded.

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 a full output schema and complete annotations, the definition needs only to convey purpose and inputs, which it does. A brief note on the underlying funnel assumptions or limitations would make it fully self-sufficient for a calculation tool.

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 each field already documents units and formats (plain-dollar strings, percentages where 80 means 80%). The phrase 'your own funnel assumptions' reinforces that all values are caller-supplied but adds no unit, range, or edge-case meaning beyond the schema.

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 ('Estimate') and names the exact quantities produced (clicks, signups, customers) plus the goal (recover a sponsorship cost) and the input basis ('your own funnel assumptions'). That is far more specific than the tool name alone and no sibling tool in the list performs break-even math, though the description never explicitly contrasts itself with adjacent cost/comparison tools.

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 only implied: an agent can infer this is for sponsorship ROI evaluation and that all five funnel inputs must be supplied by the caller. There is no statement of when to prefer it over alternatives (e.g. toolfound_software_cost_comparison) or when it should not be used, so guidance remains implicit.

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.

Resources