Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Ranking change: like for like or mix

webops_position_change
Read-onlyIdempotent

Did rankings really fall? Average position in two windows split into like for like, re-weighting, new and lost pairs, with a noise band; pairs moved by more than 2; impressions and clicks to tell position, demand or click loss. 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_position_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoBreak each part down by query, page or device.
daysNoWindow length in whole weeks of days (7, 14, … 182; default 28), ending on the latest day with data, against the same number of days before.
pageNoOne page, exactly as webops_pages returns it.
limitNoHow many of the biggest movers each way (default 5).
queryNoOnly this search.
domainYes
after_toNoLast day of the later window (same length as the earlier one).
before_toNoLast day of the earlier window.
after_fromNoFirst day of the later window.
before_fromNoInstead of days: first day of the earlier window (give all four).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive, so the bar is lower and the description still adds real information: the noise band warns results are statistical, the like-for-like vs re-weighting split explains how the comparison is computed, and "another organization's or an unconnected site answers not found" discloses a specific failure mode. It stops short of stating pagination or the exact result shape, but the behavioral context is above typical for this tier.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is compact and front-loads the core question, with no filler sentences. The semicolon-chained fragments are compressed to the point of ambiguity, though — "pairs moved by more than 2" and "impressions and clicks to tell position" require re-reading, which costs clarity for the size saved.

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 correctly spends its words describing what comes back (like-for-like, re-weighting, new and lost pairs, noise band, biggest movers each way) and adds the out-of-scope failure behavior. For a 10-parameter read tool with high schema coverage, the remaining gaps (enum values for by, interaction of days with the four explicit date fields) are minor.

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 90% with 10 parameters, so the schema already carries the parameter burden and baseline 3 applies. The description adds meaning at the aggregate level (default 28-day window ending on the latest day with data, compared against the same number of prior days; "pairs moved by more than 2" links to the movers limit) but does not clarify the by enum values, query, or page semantics beyond what the schema states.

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 makes the resource unmistakable: average position compared across two windows, decomposed into like-for-like, re-weighting, new and lost pairs, with a noise band and top movers. It is not a crisp verb+resource statement (it opens with a question and reads as a list of outputs), but an agent can still tell this apart from webops_compare, webops_daily and webops_breakdown by the two-window decomposition framing.

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?

"Did rankings really fall?" implies the trigger (a suspected ranking drop) and "impressions and clicks to tell position, demand or click loss" implies the diagnostic follow-up, so usage is reasonably inferable. However, no sibling is named as an alternative and there is no explicit when-not guidance; the note about other organizations returning not found is a scope/error constraint rather than usage guidance.

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