Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Shop: items and pages that earn

webops_shop
Read-onlyIdempotent

For a website that sends shop events, over the analysis window: totals (visits, adds to cart, checkouts, purchases, revenue), the items earning most (viewed, added, checked out, bought, revenue) and the landing pages earning most. Says when the site sells nothing. 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_shop"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many items and landing pages, most revenue 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 declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety needs no restating. The description adds genuinely non-obvious behavior: the empty-result case ('says when the site sells nothing') and the cross-organization/unconnected-site 'not found' response. The only gap is that it does not describe the shape of the response beyond the metric list.

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?

The output payload (totals, items, landing pages) is front-loaded, and the caveats about empty sites and not-found cases follow in short sentences. The parenthetical metric lists are dense but each term maps to a returned field, so nothing is padding. Slightly heavy punctuation keeps it from a 5.

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?

There is no output schema, so the description carries the burden of describing returns, and it enumerates the totals and both ranked lists. It also covers the two most important failure modes (no shop events, wrong/unconnected site). What is missing is a definition of the 'analysis window' and whether results are aggregated per item vs per page, but overall it is complete enough to call correctly.

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 50%: the limit parameter is fully documented in the schema (default 20, max 100, most revenue first), while domain has no schema description. The description compensates partially by framing the call around a website and noting that another organization's site returns not found, which implies domain scoping and permission semantics. It adds no detail about limit ordering or default, but that is already in the schema, so a baseline 3 is appropriate.

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 the specific resource and scope: shop-event totals (visits, adds to cart, checkouts, purchases, revenue), top-earning items, and top-earning landing pages. That is far more precise than the title alone and lets an agent distinguish it from generic analytics siblings such as webops_pages or webops_breakdown. It stops short of naming an explicit alternative, so it is clear but not fully differentiated.

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 precondition 'For a website that sends shop events, over the analysis window', which tells the agent the site must have ecommerce tracking. The description also covers two edge outcomes ('says when the site sells nothing', 'not found' for another org's or an unconnected site). However, it never states when to prefer this tool over a sibling like webops_breakdown or webops_pages, so guidance remains implied rather than explicit.

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