Skip to main content
Glama

BRAINIAC Website Conversion Intelligence

Check conversion event coverage

conversion-intelligence_event-coverage-check

Compare expected tracking events with supplied event counts. Missing or zero events are flagged. No analytics account is accessed. Price $0.04 USDC. POST /api/v1/conversion-intelligence/event-coverage-check. 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_event-coverage-check"
  }
}

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

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

With no annotations, the description carries the full burden, and it does disclose several useful traits: no analytics account is accessed, the price is $0.04 USDC, the transport is POST /api/v1/conversion-intelligence/event-coverage-check, and unpaid calls return 402 without running. That is solid payment and failure-mode context. It still omits what happens when no input is supplied, whether the call is idempotent, and what the response contains, which matters for a 14-parameter tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, front-loaded with the core behavior, then the scoping caveat, then cost and endpoint, then the payment failure mode. Every sentence carries distinct information and there is no filler.

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 output schema, and no annotations, the description is far too thin. It never explains the input shape, which of the many data channels are expected, or what the result looks like, so an agent would have to reverse-engineer the schema to call it correctly.

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, several of them nested arrays of objects, so the description must compensate and largely does not. It only gestures at two of them, expectedEvents and the supplied event counts, leaving csv, file, json, text, forms, pages, fields, stages, funnels, sources, segments, and minSample entirely unexplained. An agent cannot tell which input channel to use or how minSample affects flagging.

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 states a specific verb and resource: compare expected tracking events against supplied event counts, flagging missing or zero events. That is concrete enough to distinguish it from the sibling analysis tools, which audit funnels, forms, and traffic sources rather than validating event coverage. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no mention of alternatives among the seven sibling tools. The only scoping statement, 'No analytics account is accessed,' clarifies what the tool does not do but does not tell an agent when to pick this over, say, analytics-funnel-analyze. Usage must be inferred entirely from the purpose sentence.

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