Skip to main content
Glama

Segment and Seat Cut Check

segment_and_seat_cut_check
Read-only

Evaluates customer segment economics and pricing safety if AI cuts seats, returning payback, CAC returns, seller capacity and seat-reduction scenarios. Use it to decide which segment to back.

Instructions

Helps you decide which customer segment to back, and whether your pricing is safe if AI cuts seats: it takes each segment's ACV, sales cycle, accounts, deal source and CAC, its logo, gross and net retention, how you charge in your own words, and your seller ramp, cost and qualified demand, and returns one page per segment with payback, gross profit per dollar of CAC, seller capacity after ramp and cycle, and the renewal if customers cut a share of seats. Ask the person to confirm the segment split, their own win rate and what customers can cut before marking each as confirmed; anything not confirmed or not given is shown as missing, never guessed. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of scale_paid_check when you need segment economics, seller capacity and seat-reduction scenarios.

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": {
      "product": "<product>",
      "segments": "<segments>"
    },
    "name": "segment_and_seat_cut_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
productYesWhat you sell, in one line. Format is text. For example, "invoice review service".
industryNoOptional: your industry, passed to the motion first draft. Format is text. For example, "manufacturing".
segmentsYesOne item per customer segment (1 to 4). Split by who signs, how they find you, sales cycle and contract value. Format is a JSON array. For example, [{"name":"an approved anonymous manufacturer"}].
confirmedNoWhat the person has confirmed. Set each to true only after asking them. Until the segment split is confirmed no sum runs. Format is a JSON object. For example, {"segment_split":true,"win_rate":true,"seat_cut":true}.
business_stageNoOptional: funding stage, passed to the motion first draft (for example series-a). Format is text.
tracks_expansionNoOptional: true only if the company tracks expansion account by account. It adds a later years table below the pages. Payback on CAC and ARR always leads. Format is true or false. For example, true.
gross_margin_percentNoGross margin as a percent (for example 72). Needed for payback and every profit sum. Format is a JSON number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.25

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the description adds substantial context on top: no sign-in, no stored inputs or outputs, hosted usage metadata recorded, and errors that name the missing or invalid field. It also discloses a behavioral rule the schema can't express — unconfirmed or absent values are shown as missing rather than guessed, and no sum runs until the segment split is confirmed.

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?

Purpose and outputs are front-loaded, and each following sentence adds a distinct fact (confirmation protocol, privacy posture, error behavior, sibling routing) with no filler. The opening sentence is very long and packs inputs and outputs together, which costs some readability, but nothing is redundant.

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 nested-schema tool with no output schema, the description carries the return-value burden well by listing what each segment page contains, and it covers privacy, errors and confirmation gating. It stops short of describing output shape or units in detail, which keeps it at 4 rather than 5.

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?

Schema coverage is 100%, so the per-field meaning is already handled; the baseline would be 3. The description adds cross-parameter semantics the schema cannot: the 'confirmed' flags are only set after asking the person, unconfirmed inputs render as missing, and the confirmation gate blocks aggregation. That is real added value beyond the field-level docs.

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 states a specific analytical job — choosing which segment to back and testing pricing safety under AI-driven seat cuts — and enumerates the outputs (payback, gross profit per CAC dollar, seller capacity after ramp, renewal under seat reduction). It also names the sibling it replaces, so an agent can distinguish it from scale_paid_check without opening either schema.

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

Usage Guidelines5/5

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

Explicit routing guidance: 'Use this instead of scale_paid_check when you need segment economics, seller capacity and seat-reduction scenarios.' It also prescribes the workflow — ask the person to confirm segment split, win rate and cuttable items before marking confirmed — which tells the agent both when and how to invoke it.

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