Skip to main content
Glama

BRAINIAC Website Conversion Intelligence

Analyze form abandonment

conversion-intelligence_form-abandonment-analyze

Measure form completion and field abandonment from supplied starts, completes, and field counts. Differences are associations in the numbers, not proven causes. Price $0.04 USDC. POST /api/v1/conversion-intelligence/form-abandonment-analyze. 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_form-abandonment-analyze"
  }
}

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?

No annotations are supplied, so the description carries the full behavioral burden, and it does disclose several non-schema traits: a $0.04 USDC charge, the POST endpoint, and that unpaid calls return 402 and do not execute. It also flags the epistemic limit that differences are associations, not proven causes, which usefully sets expectations for the output; what it omits is any hint about the response shape or how minSample affects results.

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?

Four short sentences, front-loaded with the purpose and followed by the caveat and the billing/endpoint facts; nothing is padded or repeated. The operational line about 402 is slightly bolted on but still earns its place.

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 nested objects, no annotations, and no output schema, the description is thin: it does not tell the agent how to choose among the four input formats or what the analysis returns. The payment and endpoint facts are helpful, but the input-shape burden is the dominant gap here.

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, including nested objects, yet the description only gestures at starts/completes/field counts. It never explains the four mutually exclusive input channels (csv, json, text, file), nor minSample, expectedEvents, forms, pages, segments, sources, stages, or funnels, leaving most of the surface undocumented in both places.

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 gives a specific verb ('Measure') and resource ('form completion and field abandonment') plus the input basis (starts, completes, field counts), so an agent can tell it is a quantitative abandonment calculator rather than a page or funnel auditor. It does not name or differentiate against the nearby siblings (funnel-analyze, landing-page-dropoff-detect), which keeps it 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 Guidelines3/5

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

Usage is only implied: the tool is for measuring form completion/abandonment once you already have starts, completes, and field counts. There is no statement of when to prefer it over conversion-intelligence_analytics-funnel-analyze or landing-page-dropoff-detect, and no prerequisites or exclusions beyond the payment note.

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