Skip to main content
Glama

Staats

by io.github.MrViolets

Conversion funnel

funnel
Read-only

Ordered conversion funnel across up to 5 steps within the period. Each step is a pageview path ({kind:'path', value:'/pricing'}) or a custom event ({kind:'event', value:'signup'}); a visitor counts for step N only after completing step N-1. Visitor identity rotates daily for privacy, so journeys spanning multiple days undercount (strongest for same-visit conversion). If site context has a stored funnel, run those steps when asked how the site is doing and compare against the previous period.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoISO end, alternative to period
fromNoISO start, alternative to period
siteNothe site's data-site code, from its script tag or list_sites. Omit when the account has a single site. In a tracked project, read the code from the script tag before asking the user.
stepsYesordered funnel steps, each a pageview path or a custom event name
periodNorelative period like '24h', '7d' (default), '4w'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteYes
funnelYes
periodYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses critical behavior: visitors only count for step N after completing step N-1, and daily identity rotation undercounts multi-day journeys. This is exactly the kind of behavioral nuance an agent needs to interpret results correctly. It adds substantial value 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?

Three sentences deliver the core definition, step semantics, caveat, and usage guidance without redundancy. The most important information is front-loaded, and every sentence earns its place.

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

Completeness5/5

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

For a read-only tool with an output schema and 100% schema param coverage, the description covers the essential nuances: step ordering, step types, identity rotation bias, and when to use stored funnel steps. Nothing critical is missing for correct invocation or interpretation.

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

Parameters4/5

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

Schema description coverage is 100%, so the schema already documents each parameter. The description adds meaning by explaining the step object format with concrete examples and the sequential counting condition, which is not present in the schema. It does not add much to period/from/to/site, but the schema handles those adequately.

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 identifies the tool as an ordered conversion funnel across up to 5 steps, with each step either a pageview path or custom event. This is a specific, distinct resource that differentiates it from siblings like journeys, get_overview, and query. The purpose is immediately understandable even without opening the schema.

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

Usage Guidelines4/5

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

The description gives explicit usage context: run stored funnel steps when asked how the site is doing and compare against the previous period. It also explains the daily identity rotation caveat that affects interpretation. However, it does not explicitly state when not to use this tool or name alternative tools for related needs.

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

All Staats toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools target clearly distinct resources or analytic questions: site CRUD, annotation handling, overviews, funnels, journeys, and diagnostic checks are separated. A few tools like get_overview, query, and what_changed could overlap when asking 'what happened', but their descriptions differentiate the intended use well.

Naming Consistency3/5

The CRUD tools follow a clean verb_noun pattern (create_site, delete_site, list_sites, update_site_context), but analysis tools mix bare nouns (funnel, journeys), bare verbs (query), adverb-verb compounds (compare_around), and what_* question phrases (what_broke, what_changed). Naming is readable and snake_case is consistent, but the overall convention is not uniform.

Tool Count5/5

15 tools is within the well-scoped range and each tool earns its place: site management, annotation tracking, traffic overview, discovery, diagnostics, and comparison all have dedicated tools. There is no obvious redundancy or padding.

Completeness4/5

The surface covers the core domain well: sites can be created, listed, deleted, and contextualized; annotations can be recorded and listed; analytics support overview, breakdown, funnel, journey, and anomaly questions. Minor gaps exist such as no update/delete for annotations and no single-site getter separate from list_sites, but agents can work around these.

Resources