Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Where a change sits

webops_breakdown
Read-onlyIdempotent

Where a change in a count sits: by search, page, topic, device, channel or event, each group's change and share of the total, biggest first. No country or language split: for visitors by country and language (Analytics) use webops_visitors. A scope with no data says so in empty. Not whether it is beyond noise (webops_compare) or why. 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>",
      "metric": "<metric>",
      "by": "<by>"
    },
    "name": "webops_breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
byYesquery, page, topic, device, channel or event. country and search_feature answer that they are not held (countries: webops_visitors).
pageNoOne page, exactly as webops_pages returns it.
limitNoHow many groups (default 10); the rest are summed.
queryNoOne search, as webops_searches returns it.
topicNoA topic in a few words: the searches sharing its topic words.
domainYes
metricYesA count: clicks, impressions, sessions, engaged_sessions or conversions.
channelNoAn Analytics channel, e.g. Organic Search, Direct.
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

A4.3/5.0
Behavior4/5

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

Annotations already carry readOnly/idempotent/non-destructive/closed-world, so the bar is lower, yet the description adds real behavior: empty scopes surface as `empty`, and out-of-scope domains return not found. It stops short of explaining how the before/after windows interact or what ordering/limit omissions do, and 'Read-only.' merely restates the annotation.

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?

Front-loaded with the core operation, then routing exclusions, then caveats — a sensible order with no filler sentences. Some fragments are telegraphic ('or why'), and the closing 'Read-only.' duplicates the annotation without adding 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?

For a 12-parameter, no-output-schema tool it covers purpose, alternative tools, aggregation ordering, and the empty/not-found outcomes, while the schema carries parameter detail. The main residual gap is that the two-window comparison semantics (equal lengths, all four dates) are left entirely to the schema rather than reinforced in prose.

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 92%, so the schema already documents `by` (including that country and search_feature answer 'not held'), the four window parameters, `limit` defaulting and summing the remainder, and the webops_pages/webops_searches formats. The description adds essentially no parameter-level meaning beyond that, so the baseline of 3 applies.

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 names the specific operation (locating where a count's change sits) and enumerates the split dimensions (search, page, topic, device, channel, event) plus the output shape (each group's change and share, biggest first). It also explicitly separates itself from webops_visitors (country/language) and webops_compare (significance), so an agent can discriminate without opening schemas.

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

Usage Guidelines5/5

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

Negative routing is explicit and paired with the correct alternative in both cases: no country/language split -> webops_visitors, and not a significance verdict -> webops_compare. It also states the failure condition (another organization's or unconnected site answers not found), leaving little to infer about when this tool is the right call.

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