Skip to main content
Glama

BRAINIAC Website Conversion Intelligence

Compare conversion segments

conversion-intelligence_segment-compare

Compare segment conversion rates only when both samples meet the disclosed minimum size. Rate differences are not treated as causation. Price $0.05 USDC. POST /api/v1/conversion-intelligence/segment-compare. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "conversion-intelligence_segment-compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
textNo
formsNo
pagesNo
eventsNo
fieldsNo
stagesNo
funnelsNo
sourcesNo
segmentsNo
minSampleNo
expectedEventsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description usefully discloses pricing ($0.05 USDC), the HTTP endpoint, the 402 payment gate that prevents execution, and the statistical caveat that differences are not causation. It still says nothing about the response shape, what happens when the sample threshold fails, or the two distinct input modes (structured segments vs raw csv/json/text).

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?

Five short sentences, front-loaded with the statistical guardrail and free of filler. The price/endpoint/payment sentences are operational and earned, though the endpoint path restates the tool name and could be compressed.

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?

For a 14-parameter tool with zero schema descriptions, no annotations and no output schema, the description covers only cost, endpoint and one precondition. An agent cannot tell from the definition which of the four content inputs to supply or what the comparison returns.

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% across 14 parameters, so the description must compensate. It only obliquely touches 'segments' and 'minimum size' (minSample); it never explains the mutually exclusive csv/file/json/text ingestion paths, the forms/pages/funnels/stages arrays, or expectedEvents.

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 and resource: 'Compare segment conversion rates'. It is distinguishable from siblings like form-abandonment-analyze or traffic-source-quality-analyze by naming segments and rate comparison explicitly, though it never names an alternative tool directly.

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?

It gives a real precondition - both samples must meet the disclosed minimum size - which tells the agent when the comparison is valid. However it gives no guidance on when to pick this tool over the sibling analyses, nor what to do if the minimum isn't met.

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