Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Compare two windows against normal variation

webops_compare
Read-onlyIdempotent

Is a change real? Two windows of a metric (site, page, search, topic, device, channel or event), its change, and whether it is beyond the site's own normal variation, with a reading. Says when it cannot judge. Not 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>"
    },
    "name": "webops_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOne page, exactly as webops_pages returns it.
eventNoOne conversion event, e.g. contact_form_submitted.
queryNoOne search, as webops_searches returns it.
topicNoA topic in a few words: the searches sharing its topic words.
deviceNodesktop, mobile or tablet.
domainYes
channelNoAn Analytics channel, e.g. Organic Search, Direct.
metricsNoComma-separated: clicks, impressions, ctr, position, sessions, engaged_sessions, engagement_rate, conversions (default all).
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.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, so the bar is lower, and the description still adds real behavior: it reports when it cannot judge, and returns not-found for another organization's or an unconnected site. This tells the agent how to interpret empty or refused results, which the annotations do not. Saying "Read-only" repeats the annotation but is harmless.

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 pivotal question is front-loaded and the definition is short for a 12-parameter tool. The clipped sentence fragments ("Says when it cannot judge. Not why.") are efficient rather than padded. Minor choppiness costs nothing material.

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 read-only comparison tool with 92% schema coverage and no output schema, the description covers the dimensions compared, the nature of the result (the change plus whether it exceeds normal variation, with a reading), and the not-found behavior. The remaining gaps, such as the equal-window-length requirement, are handled in the schema text.

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 each parameter, including the four date fields and the comma-separated metrics list. The description adds only the enumeration of filterable dimensions and "two windows", without clarifying the equal-length window constraint or defaults beyond what the schema states. 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 states a specific comparison: two windows of a metric compared against the site's own normal variation, with a judgment and a reading. It enumerates the dimensions (site, page, search, topic, device, channel, event), which pins down the resource. It stops short of naming a sibling such as webops_rankings_compare, so differentiation is inferred rather than stated.

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?

Opening with "Is a change real?" implies the use case and the phrase "Not why" steers the agent away from expecting causal diagnosis, which is a soft exclusion. However, no alternative tool is named for the causal question, and there is no explicit when-not-to-use guidance beyond the cross-organization/not-found constraint.

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