Skip to main content
Glama

BRAINIAC Website Conversion Intelligence

Analyze traffic source quality

conversion-intelligence_traffic-source-quality-analyze

Calculate conversion rates by supplied traffic source. Ranking uses only sources that meet the disclosed sample minimum and does not claim causation. Price $0.05 USDC. POST /api/v1/conversion-intelligence/traffic-source-quality-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_traffic-source-quality-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.2/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 substantial work: it discloses the $0.05 USDC price, the POST endpoint, the 402 failure mode where unpaid calls do not run, and two important statistical behaviors (sample-minimum gating of the ranking and a no-causation claim). It does not describe the response shape or which input payload form is accepted.

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 with the purpose front-loaded and no filler; each clause carries information about cost, transport, or statistical guardrails. The verbatim route duplicates the tool name in machine form and could be trimmed without loss, keeping it just below a top score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Payment, statistical guardrails, and the endpoint are well covered, but for a 14-parameter tool with nested objects and no output schema, the description never explains the input contract — that content arrives as one of csv/json/text/file or as structured `sources`/`segments` arrays — nor what the ranking returns. Adequate on behavior, incomplete on invocation.

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 a nested file object and eight structured data arrays, so the description must compensate and largely does not. It hints at the `sources` array ("by supplied traffic source") and obliquely at `minSample` ("disclosed sample minimum"), but never explains the csv/json/text/file alternatives or which input the tool expects.

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?

Uses a specific verb plus resource: "Calculate conversion rates by supplied traffic source." That is far more informative than the name alone and distinguishes it from funnel-analyze or segment-compare by the unit of analysis (traffic source). It stops short of naming an explicit sibling alternative, so it is clear but not fully differentiating.

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 or when-not-to-use guidance relative to the other conversion-intelligence analyses; the agent must infer from the resource noun that this is the source-quality view. The only conditional statement concerns payment (unpaid calls return 402), which is a precondition, not usage guidance.

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