Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Everything about one page

webops_page_dossier
Read-onlyIdempotent

One page, everything: what the crawl read, its searches and weekly positions, visits and conversions, index verdicts, speed, links in and out, lookups showing it, its findings and decisions, and dated changes. Evidence, not a cause. 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>",
      "page": "<page>"
    },
    "name": "webops_page_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD. Default: the 28 days ending on the latest day with data.
fromNoFirst day, YYYY-MM-DD. Default: the 28 days ending on the latest day with data.
pageYesThe page, as webops_pages returns it.
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavior: cross-organization or unconnected sites return 'not found', and the payload is raw evidence with no causal analysis. It says nothing about response shape, size, or pagination for a tool that aggregates many data classes.

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 core promise 'One page, everything'. The middle sentence is a dense enumeration that is informative but breathless; every clause does map to a real section of the response, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does the heavy lifting by enumerating the returned sections, and it discloses the key edge case (not-found for out-of-scope sites). Together with the schema's documented date defaults, an agent has enough to call it and interpret it correctly for a read-only aggregate.

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 coverage is 75% and the two date parameters carry their own defaults in the schema; the only gap is `domain`, which has no schema description. The description adds no syntax or format detail beyond implying a single page is targeted, so the baseline 3 applies.

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?

Specific verb-less but precise scope: 'One page, everything' followed by an enumeration of the exact sections returned (crawl read, positions, visits/conversions, index verdicts, speed, links, lookups, findings, changes). An agent can tell this is the single-page aggregate view rather than a list tool like webops_pages. It stops short of naming which sibling to use for a narrower slice (e.g. webops_pagespeed, webops_links), so it is clear but not fully differentiated.

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?

'Evidence, not a cause' implicitly tells the agent to use this for gathering facts about a page rather than for diagnosis, and the not-found note tells it when the call will come back empty. There is no explicit when-to-use/when-not guidance versus the narrower per-topic siblings (webops_pages, webops_pagespeed, webops_links), so the routing is left to inference.

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