Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Broken links visited, stopped hours, events, forms

webops_analytics_health
Read-onlyIdempotent

From the extra Analytics reports: not-found addresses visitors reach and where from, the last hours' visits and conversions against their norm, which events the site sends, and form starts and sends per page with completion. 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_analytics_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

B3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety burden is largely covered. The description adds real value beyond that: it discloses the error behavior for foreign or unconnected domains and enumerates which report families are returned, which the annotations cannot express.

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?

One dense sentence plus a short constraint sentence, with the report inventory up front and no filler. The opening 'From the extra Analytics reports' is slightly opaque and the four-item list reads as a run-on, but nothing is wasted.

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

Completeness2/5

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

This is a bundle of four distinct report types with no output schema, so the agent has no idea of return shape, pagination, or per-report structure. The description lists contents but gives no guidance on how the four reports are combined or keyed, leaving a complex tool under-specified.

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 0%, so the single required 'domain' parameter is undocumented in the schema (only pattern and length constraints are given). The description only indirectly implies it identifies the site being queried via the 'another organization's or an unconnected site' sentence; it never states accepted domain formats or whether scheme/subdomain is expected.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names four distinct report contents (404s with referrers, hourly visits/conversions vs. norm, events, form starts/sends per page), so an agent learns what data comes back, but the verb is only implied ('From the extra Analytics reports') and nothing distinguishes this from siblings like webops_links or webops_breakdown, which plausibly overlap with the 404 portion.

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

Usage Guidelines2/5

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

No statement of when to call this versus alternatives such as webops_links, webops_breakdown, or webops_daily, despite heavy apparent overlap. The only contextual guidance is a failure condition ('Another organization's or an unconnected site answers not found'), which helps avoid misfires but is not usage guidance.

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