Skip to main content
Glama

get_cac_benchmark

Read-only

Use when evaluating sales and marketing efficiency, setting CAC targets, or benchmarking GTM performance before a board review. Returns CAC payback ranges, LTV/CAC guardrails, and channel efficiency benchmarks by industry and GTM motion. Example: Mid-market SaaS with field sales — median CAC payback 22 months, LTV/CAC 3.8x — organizations above 30-month payback face capital efficiency pressure from investors. Source: Stratalize go-to-market composite. $0.02 USDC per call.

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": {
      "industry": "<industry>"
    },
    "name": "get_cac_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryYesIndustry vertical
gtm_motionNo
avg_contract_value_usdNoACV for LTV:CAC calculation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already establish read-only, open-world, non-destructive behavior. The description adds meaningful context beyond that by naming the data source, disclosing a $0.02 per-call cost, and illustrating typical metric ranges and investor interpretation. It does not disclose data freshness or coverage limitations.

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?

The description is front-loaded with when to use the tool, then states what it returns, gives a concrete example, and closes with source and cost. Every sentence provides useful selection or interpretation context without redundant repetition.

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?

For a three-parameter, read-only benchmark tool with no output schema, the description covers the use cases, returned metric categories, a concrete example, source, and per-call cost. It could add data vintage, geography, or units, but it is largely complete for correct invocation.

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?

The description clarifies that benchmarks are segmented by industry and GTM motion and that LTV/CAC is relevant, which adds some meaning beyond the enum labels. However, with 67% schema coverage, it does not fully explain the role or optionality of avg_contract_value_usd or how ACV affects the returned benchmark.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifies a concrete benchmark resource: CAC payback ranges, LTV/CAC guardrails, and channel efficiency benchmarks by industry and GTM motion. This clearly distinguishes it from the many other benchmark sibling tools by its CAC and GTM-efficiency focus.

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

Usage Guidelines4/5

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

It gives clear triggering scenarios: evaluating sales and marketing efficiency, setting CAC targets, benchmarking GTM performance, and preparing for board review. It does not state when not to use it or name alternative tools, so it stops short of full routing guidance.

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