Skip to main content
Glama

Stratalize Intelligence

Get Cac Benchmark

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. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, open-world behavior. The description adds useful behavioral detail beyond that: the returned metric families, a concrete example, the data source, and the $0.02 per-call cost. It does not cover data freshness or limits, but it is strong for a read-only benchmark lookup.

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?

The description is front-loaded with usage and return content, followed by an example and source/cost details. It is well structured, though the example includes some interpretive framing that is slightly more verbose than needed for tool invocation.

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 no output schema, the description appropriately explains what is returned. Three parameters with one required is relatively simple, and the key segmentation dimensions are covered. Minor gaps around gtm_motion option meaning and ACV behavior are partly handled by the schema.

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

Parameters4/5

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

The description says results are segmented 'by industry and GTM motion,' which adds meaning beyond the schema, especially for the undocumented gtm_motion parameter. The example also clarifies segment usage. avg_contract_value_usd is left to the schema description, which is sufficient.

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 clearly states the tool returns CAC payback ranges, LTV/CAC guardrails, and channel efficiency benchmarks, which distinguishes it by topic from the many sibling benchmark tools. It does not explicitly contrast itself with those siblings, so it stops short of a 5.

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 concrete when-to-use guidance: evaluating sales and marketing efficiency, setting CAC targets, and benchmarking GTM performance before a board review. It does not state when not to use it or name alternative tools, but the usage context is clear.

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