Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Where visitors go, page to page

webops_journeys
Read-onlyIdempotent

Every page's views, engagement time per view and devices (not only landing pages), and one-step flows: where visitors came from, where they went next, how many left. One step only: full paths are not available. 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_journeys"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOne page: a path (/pricing) or an address of the site. Default: the busiest pages.
limitNoHow many pages, busiest first (default 20).
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 read-only, idempotent, non-destructive and closed-world, so the bar is lower; the description still adds real context by disclosing that another organization's or an unconnected site returns 'not found'. It also warns that only one hop is available, which prevents an agent from assuming full-path traversal. Return-column details and aggregation windows are not spelled out.

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 front-loaded: the payload comes first, the one-step constraint and the not-found behavior follow, and the read-only flag closes it. Fragmented phrasing ('One step only: full paths are not available') reads like clipped notes but each clause carries information.

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 the return shape, and it does: metric list plus entry/next/exit counts. It also covers the main failure mode for an out-of-scope domain. Missing pieces are aggregation period and how page/limit shape the output, which are minor for a reporting tool.

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 description coverage is 67%: page and limit are documented in the schema, while domain carries a regex/length constraint but no prose. The description adds nothing about parameter behavior (e.g., what happens when page is out of the busiest set, or how limit interacts with one-step flows), so this is the baseline for partially covered schemas.

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 enumerates the concrete payload: per-page views, engagement time per view, device breakdown, and one-step entry/next/exit flows. It explicitly scopes itself away from landing-page-only data and from full-path analysis, so an agent can tell it is a page-level journey report. It stops short of naming any sibling tool, so the boundary with webops_pages or webops_funnel_steps must be inferred.

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 implied by the data described ('not only landing pages', 'one step only'), which tells the agent this is not a path-analysis tool, but there is no explicit when-to-use or when-not-to-use statement and no named alternative. The closest thing to a routing rule is the one-step limitation.

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