Skip to main content
Glama

Email Delivery to Purchase Funnel

bpj_email_delivery_purchase_funnel
Read-onlyIdempotent

Compute delivered messages, click rate among deliveries, click-to-purchase conversion and purchase rate per send.

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": {
      "sent": "<sent>",
      "bounced": "<bounced>",
      "clicked": "<clicked>",
      "buying": "<buying>"
    },
    "name": "bpj_email_delivery_purchase_funnel"
  }
}

Input Schema

NameRequiredDescriptionDefault
sentYes
buyingYes
bouncedYes
clickedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 a set of derived rates, but it does not mention any edge-case behavior (e.g., what happens if bounced >= sent, or if buying exceeds clicked) that would matter for a pure calculation tool.

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 sentence that front-loads the verb and lists the outputs in funnel order. No filler, no restatement of the title, and nothing that could be trimmed without losing information.

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?

With four required numeric parameters, no output schema, and zero schema coverage, the description should carry more weight. It says which metrics come out but not their precise definitions or output shape, so an agent still has to guess at formula details and return format.

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%, so the schema offers only short titles. The description partially compensates by tying each metric to a parameter role — deliveries derive from sent/bounced, clicks are measured among deliveries, buying is set against clickers and against sends — which clarifies how the four inputs relate. It stops short of stating the arithmetic or valid-range expectations.

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 (compute) and enumerates the exact metrics produced: delivered messages, click rate among deliveries, click-to-purchase conversion, and purchase rate per send. It is clear what the tool does, but it makes no attempt to distinguish itself from closely related siblings such as bpj_funnel_backsolve or bpj_failed_delivery_cost.

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 by the metric names; there is no explicit statement of when to use this rather than the funnel/backsolve or failed-delivery-cost siblings. The agent can infer this is the forward funnel calculator, but nothing in the text confirms or excludes that reading.

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.