Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Funnels: people at each step

webops_funnel_steps
Read-onlyIdempotent

The website's funnels (its own steps, else built from its goal, page types and conversion events): people reaching each step in the last 28 days and the 28 before, the share going on at each step, by device and channel, and where people went next. Says when the funnel report is unavailable. Another organization's or an unconnected site answers not found. Read-only.

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": {
      "domain": "<domain>"
    },
    "name": "webops_funnel_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, and closed-world, but the description adds real behavioral context beyond them: the funnel may be the site's own steps or synthesized from goal, page types, and conversion events; the window is 28 days plus the prior 28; and it discloses two failure modes (report unavailable, not found for foreign/unconnected domains).

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?

Dense but efficient: the payload is front-loaded, followed by short sentences for fallback construction and error behavior. The opening clause is a long parenthetical that slightly obscures the core 'returns funnel step data' claim, but nothing is wasted.

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?

With no output schema, the description must convey return content and does so concretely (counts, shares, device/channel segmentation, next-step paths, period comparison) along with error states. It leaves the exact response shape and whether an unconfigured funnel always yields a synthesized one unstated, which are the only notable gaps.

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 0%, so the description carries the burden, and it does partially: 'the website's funnels' plus the not-found rule for another organization's or unconnected site conveys that the domain must be a connected site owned by the caller. It still gives no hint about the accepted domain format (hostname pattern, 3-253 chars) or whether a bare domain versus URL is expected.

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 names a specific resource (the website's funnel steps) and enumerates exactly what is reported: people per step, prior-period comparison, step-to-step share, device/channel split, and next-step destinations. It never names a sibling, but the closing 'Read-only' implicitly separates it from webops_set_funnel_steps.

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?

Usage is only implied through the read-only framing and the note that other organizations' or unconnected sites return not found. There is no explicit 'use this when...' or routing to an alternative such as a breakdown or journeys tool for the same question.

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