Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

What kind of website it is

webops_site_profile
Read-onlyIdempotent

What kind of site a connected website is: page types, structured data, search intents and brand terms, from the latest crawl and 90 days of Search Console. 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_site_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (which already declare read-only, idempotent, closed-world), the description adds genuinely useful facts: the data provenance (latest crawl plus 90 days of Search Console) and the not-found behavior for another organization's or unconnected sites. It does not describe response shape or freshness beyond the crawl caveat, but the added context is substantive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with what the tool returns and followed by the failure condition. No filler or redundant restatement of the title.

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?

For a single-parameter, read-only tool with no output schema, the description covers sources, scope of returned categories, and the failure mode, which is close to sufficient. The only material omission is any clarification of what the domain argument must be for the call to succeed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never explains the sole required parameter 'domain' — no statement of whether it must be a bare hostname, whether it must already be connected, or how it relates to the 'connected website' it profiles. The connection requirement is only hinted at obliquely via the not-found sentence.

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?

The description names a specific verb and resource ('what kind of site a connected website is') and enumerates contents: page types, structured data, search intents, brand terms, drawn from a crawl plus 90 days of Search Console. It is clear on its own, though it never explicitly contrasts itself with near-neighbors such as page-level or breakdown tools.

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 — the agent can infer this is the tool for a high-level site characterization. There is no explicit when-to-use versus when-not, and no named alternative for per-page detail or search-term analysis, so routing between siblings still requires 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