Skip to main content
Glama

BRAINIAC Website Conversion Intelligence

Report conversion diagnostics

conversion-intelligence_diagnostics-report

Combine funnel drop-offs, page exits, event coverage, source rates, form abandonment, and segment comparisons from supplied counts. No traffic or revenue is invented. Price $0.12 USDC. POST /api/v1/conversion-intelligence/diagnostics-report. 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_diagnostics-report"
  }
}

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.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses that no traffic or revenue is invented, that calls cost $0.12 USDC, and that unpaid calls return 402 and do not run, but it does not describe side effects, storage behavior, or return behavior.

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 the main purpose, then adds practical constraints about pricing and payment failure. It is reasonably tight, though the endpoint and payment details make it slightly operational rather than purely explanatory.

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?

This is a complex tool with 14 parameters, nested objects, no output schema, and no annotations, so the description needs to do substantial work. It explains the high-level purpose and payment behavior, but it leaves major gaps around parameter semantics, expected input structure, and the shape of the diagnostics report.

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?

The schema has 14 parameters with 0% description coverage, and the description does not map any parameter names to meaning or format. It hints at the input domains (funnels, pages, events, sources, forms, segments) through its list of analyses, but it does not explain how to use csv, json, text, file, minSample, expectedEvents, or the nested structures.

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 names a specific action ("Combine") and resource (a diagnostics report) and lists the six analyses it aggregates: funnel drop-offs, page exits, event coverage, source rates, form abandonment, and segment comparisons. This makes its role distinct from the narrower sibling analysis tools.

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 wording implies the tool is for producing a combined diagnostics report from supplied counts, and it states that unpaid calls do not run. However, it gives no explicit guidance on when to choose this aggregate report over the sibling tools for funnel analysis, event coverage, form abandonment, and similar tasks.

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