Skip to main content
Glama
Marketing Ops MCP

Marketing Ops MCP

calculate_funnel

Read-onlyIdempotent

Calculate explicit-denominator conversion and acquisition metrics for a single cohort to assess funnel performance and acquisition efficiency.

Instructions

Calculate explicit-denominator conversion and acquisition metrics for one cohort.

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": {
      "payload": "<payload>"
    },
    "name": "calculate_funnel"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds no behavior beyond them — nothing about the meaning of cohort_confirmed as a gate, how string-typed spend/revenue are coerced, or how currency affects the computation.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though efficiency here partly reflects under-specification rather than disciplined editing.

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

Completeness2/5

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

A seven-field required payload with no field documentation, no output schema, and no explanation of which metrics are returned or in what form. For a calculation tool whose whole value is the returned metric set, one sentence is not sufficient for an agent to invoke it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across a payload object with seven required fields, so the description carries the full burden and does not meet it. "Explicit-denominator" and "one cohort" faintly gesture at cohort_confirmed and the visitors/leads/customers denominators, but spend, revenue, and currency semantics — notably that spend/revenue accept either a number or a string — are never explained.

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?

States a specific verb ("Calculate") and a specific output class (conversion and acquisition metrics) scoped to "one cohort." The phrase "explicit-denominator" is domain jargon but does distinguish it from a generic metrics lookup, and none of the siblings (analyze_experiment, design_experiment, reconcile_transactions, build_campaign_url) overlap with funnel calculation.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus the experiment-analysis siblings, no prerequisites, and no note on what state the cohort must be in. Usage is only implied by the verb "Calculate," leaving the agent to guess whether this is a pre-experiment sizing step or a post-hoc reporting step.

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