Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

What changed, and when

webops_timeline
Read-onlyIdempotent

Dated events in a window, newest first: page changes, new, removed or redirected pages, noindex, canonical, index verdicts, sitemaps, speed, lost links, applied fixes, tracking changes, results-page features, Google updates. Each dated between two observations. None in the window says so in empty. A lead, not proof. 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_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD. Default: the 28 days ending today.
fromNoFirst day, YYYY-MM-DD. Default: the 28 days ending today.
pageNoOne page, exactly as webops_pages returns it.
kindsNoComma-separated kinds to keep, e.g. page_changed,noindex_on,google_update.
limitNoHow many events, newest first (default 200).
domainYes
path_prefixNoOnly pages under this path, e.g. /blog.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description still adds real behavioral context beyond them: newest-first ordering, the fact that each event is dated between two observations (precision limits), that an empty window is signalled in `empty`, and the epistemic caveat 'A lead, not proof' — i.e. events are correlated signals, not causal proof.

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 claim and the ordering, then the event taxonomy, then the caveats. The long comma-separated kind list is dense but each item is informative; the telegraphic style ('A lead, not proof. Read-only.') is efficient rather than padded.

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?

With 7 parameters, no output schema, and a read-only annotation set, the description does the important remaining work: it tells the agent what kinds of events come back, the sort order, and how an empty result is represented. It stops short of describing individual event fields, but the taxonomy plus the `empty` note covers what an agent needs to call and interpret it.

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 86%, so the schema already documents from/to defaults, page, kinds, limit, and path_prefix. The description adds only indirect meaning — 'in a window' and 'newest first' — and does not clarify the kinds vocabulary or how page/path_prefix interact. Baseline 3 is appropriate when the schema carries the parameter burden.

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 a specific resource (dated events in a window, newest first) and enumerates the event kinds it covers — page changes, removals, redirects, noindex, canonical, index verdicts, sitemaps, speed, lost links, applied fixes, tracking changes, SERP features, Google updates. That enumeration is concrete enough to separate it from metric-oriented siblings like webops_daily or issue-oriented ones like webops_findings without opening a schema.

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 only implied: an agent can infer this is the tool for 'what happened in this date range,' and 'A lead, not proof' hints at how to treat results. But there is no explicit when-to-use versus when-not, and no sibling is named as the alternative for adjacent questions (e.g. current findings vs historical events).

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