Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Average position, two periods

webops_rankings_compare
Read-onlyIdempotent

Two periods' average position split into like for like and mix (default the last 4 weeks against the 4 before). webops_position_change adds the pairs that moved. 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_rankings_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoquery, page or device.
pageNoOne page, exactly as webops_pages returns it.
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

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the 'Read-only.' sentence is redundant. The description earns credit by disclosing default-window behavior and the failure mode: another organization's or an unconnected site returns not found. It does not describe result ordering or magnitude semantics of the mix component.

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?

Three short sentences, front-loaded with the operation and its default window before the sibling pointer and the error note. The trailing 'Read-only.' repeats what the annotations already state and could be dropped.

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 an 8-parameter tool with no output schema, the definition covers the operation, the default window, the sibling boundary, and the not-found failure mode. The only real gap is that the return structure behind 'like for like and mix' is named but not characterized, which matters when no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 88%, so the baseline is 3, and the description goes beyond it by explaining that the four date parameters are optional in favor of a default window. That resolves genuine ambiguity in the schema, where before_from is described only as an alternative to passing days. It adds no meaning for by/query/page beyond what the schema already says.

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?

States a specific verb and resource: average position for two periods, decomposed into like-for-like and mix. That decomposition is a distinctive scope signal that separates it from a plain period comparison. It does not fully disambiguate from the similarly named webops_compare sibling, which is left unmentioned.

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

Usage Guidelines4/5

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

Gives an explicit default window (last 4 weeks against the 4 before) and routes the agent elsewhere for a related need by naming webops_position_change for the pairs that moved. It stops short of stating exclusions or when this tool should not be chosen over webops_compare.

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