Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Google's index status

webops_indexing
Read-onlyIdempotent

Google's index verdict per inspected page of a connected website, and its submitted sitemaps with their counts. 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_indexing"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

B3.4/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 structurally. The description adds the useful not-found behavior for unconnected/foreign sites and hints at the return contents (per-page verdict, sitemaps with counts), but says nothing about pagination, result limits, or freshness of the index data.

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?

Two short sentences, result contents front-loaded before the access caveat. The telegraphic phrasing ('answers not found') is compact without being confusing, and nothing is wasted.

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

Completeness3/5

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

For a single-parameter read tool with full annotations this is close to adequate: it says what comes back and what happens on a bad site. It falls short on the domain value format and on any signal distinguishing this from adjacent website-level tools, which the agent still has to guess.

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?

There is one parameter, domain, with 0% schema description coverage, so the description must carry the meaning. 'Of a connected website' implies the value must identify an already-connected property, but it does not clarify whether a bare domain, subdomain, or property identifier is expected, leaving a real ambiguity given the pattern constraint.

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?

Names a specific resource pair: Google's index verdict per inspected page plus submitted sitemaps with counts, scoped to a connected website. That is meaningfully narrower than a generic site-status tool, though it never explicitly contrasts with siblings like webops_website_status or webops_pages.

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?

Gives one concrete precondition — another organization's site or an unconnected site returns not found — which tells the agent what warrants a failed call. It offers no explicit when-to-use versus the other website-level tools (status, pages, page dossier), so the choice between them 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