Skip to main content
Glama
Sign In

KrystalView Analytics

by io.github.KrystalView
OverviewDiscussionsAdmin

Analyze Funnel

get_funnel_analysis
Read-onlyIdempotent

Analyze a conversion funnel and show step reach, drop-off, and completion evidence.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "funnel_id": "<funnel_id>"
    },
    "name": "get_funnel_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLookback period in days.
funnel_idYesFunnel ID from get_funnels.

Output Schema

NameRequiredDescriptionDefault
dataYesFunnel reach, conversion, drop-off, and step-level evidence for the selected lookback period.
metaYesSite and rate-limit metadata for the current MCP call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, covering safety. The description adds detail on the output (step reach, drop-off, completion evidence), providing additional transparency beyond annotations.

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?

Single sentence that is concise and front-loaded with the action ('Analyze a conversion funnel...'). No unnecessary words.

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

Completeness4/5

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

Given the presence of an output schema, the description does not need to detail return values. It summarizes the key outputs (step reach, drop-off, completion evidence) and the tool is simple with only two parameters. Annotations cover behavioral context, so completeness is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with clear descriptions for both parameters (funnel_id from get_funnels, days lookback). The description does not add extra context beyond the schema, so baseline score of 3 is appropriate.

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 clearly states it analyzes a conversion funnel and shows step reach, drop-off, and completion evidence. This distinguishes it from sibling tools like get_anomalies or get_campaign_sessions, which focus on different metrics.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies usage for funnel analysis, but does not mention prerequisites like obtaining a funnel_id from get_funnels, though that is clarified in the schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All KrystalView Analytics toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources