Skip to main content
Glama

BRAINIAC Website Conversion Intelligence

Audit a checkout funnel

conversion-intelligence_checkout-funnel-audit

Audit supplied cart, checkout, payment, and purchase stage counts. The largest measured drop-off is reported without inventing missing steps. Price $0.05 USDC. POST /api/v1/conversion-intelligence/checkout-funnel-audit. 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_checkout-funnel-audit"
  }
}

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
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose non-obvious behavior: the output highlights the largest measured drop-off, missing steps are not fabricated, the call costs $0.05 USDC, and unpaid calls return 402 without executing. What is missing is any statement of side effects/statefulness or a fuller picture of the response beyond the single drop-off figure.

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 short, front-loaded with the purpose, and every sentence adds something (scope, output behavior, price, transport, error handling). The endpoint path and price are arguably implementation detail for a tool caller, which keeps it from a 5.

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 tool with 14 parameters, nested objects, no annotations, and no output schema, the description says almost nothing about how to shape the input payload or what the audit result contains. It covers pricing and failure behavior but leaves an agent unable to confidently construct a call.

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 14 parameters, so the description must compensate and it largely does not. The mention of 'cart, checkout, payment, and purchase stage counts' loosely points at the stages parameter, but csv, file, json, text, forms, pages, events, fields, funnels, sources, segments, minSample, and expectedEvents receive no explanation of format or expected content.

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 uses a specific verb and resource ('Audit supplied cart, checkout, payment, and purchase stage counts') and names the exact funnel domain, which distinguishes it from broader siblings like analytics-funnel-analyze. It stops short of explicitly contrasting itself with those siblings, but the checkout/payment scope is clear enough to select on.

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?

The phrase 'supplied ... stage counts' implies the caller must bring the data, and the mention of cart/checkout/payment/purchase implies the checkout-specific case. However, there is no explicit when-to-use or when-not-to-use guidance and no reference to alternatives such as form-abandonment-analyze or event-coverage-check.

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