Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Structured data and Google's rich-results verdict

webops_structured_data
Read-onlyIdempotent

Per crawled page: the structured-data types found, Google's own rich-results verdict and issues from URL Inspection (first), and the results of our rules, each naming the Google page and the day its requirement was read; plus the rule table with its weekly watch status. 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_structured_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoOne page: its JSON-LD properties too.
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.5/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 description's "Read-only" is redundant. It earns credit elsewhere: it discloses output composition and precedence ("issues from URL Inspection (first)"), provenance/recency semantics ("each naming the Google page and the day its requirement was read"), the presence of a rule table with weekly watch status, and the not-found behavior for foreign or unconnected sites. That is meaningful behavior beyond the structured fields.

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?

The returned content is front-loaded in the first clause, and the two short trailing sentences (not-found rule, read-only) are easy to scan. The opening sentence is a dense semicolon-chained list, but each clause carries distinct information rather than filler. Minor cost: "Read-only" duplicates the annotations.

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 no output schema, the description carries the return-value burden and does so well, naming each result component, its provenance field, and the rule table. It also covers the negative case. The remaining gap is the optional `page` parameter's behavior and approximate result shape/size, which matter for a domain-scoped reporting tool.

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 only 50%: `page` is documented, `domain` is not. The description partially compensates by implying `domain` must belong to the caller's organization or a connected site ("answers not found" otherwise), and "Per crawled page" plus the schema note about JSON-LD properties clarifies `page`'s role. It never states what happens when `page` is omitted (domain-wide aggregate vs. error), so the most important parameter-semantics question is left open.

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 resource and enumerates exactly what is returned per crawled page: structured-data types, Google's rich-results verdict, URL Inspection issues, our rule results with provenance, and the rule table with watch status. It is unmistakably about structured data / rich results, so an agent can separate it from siblings like webops_pagespeed or webops_indexing. It never uses an explicit verb ("returns"/"reports"), framing everything as a noun phrase, so it stops short of a 5.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative among the many siblings. The only scoping statement, "Another organization's or an unconnected site answers not found," is a precondition/error behavior rather than a routing cue. An agent must infer that this is the tool for structured-data audits purely from the field list.

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