Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

A website's setup: conversions, priority pages, competitors

webops_site_settings
Read-onlyIdempotent

The website owner's setup, read by every finding and investigation: the conversion events that are real leads (and the paths left out), the priority pages and the services they sell, and the confirmed competitors with suggestions. 'missing' names what is not confirmed yet. 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_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: cross-organization or unconnected domains return not found, and the 'missing' marker denotes unconfirmed values in the response — both material for interpreting results.

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 front-loads the resource identity and enumerates its contents efficiently, with no filler. The trailing 'Read-only.' fragment merely restates readOnlyHint=true from the annotations and earns little place.

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 one-parameter read tool with no output schema, the description does the necessary work of enumerating what the response contains and explaining the 'missing' convention. It is nearly complete, with only the exact domain input format left as a minor gap.

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?

The single domain parameter has 0% schema description coverage, so the schema only conveys format constraints (pattern, length) and not meaning. The description partially compensates by establishing that the domain must belong to the caller's organization and be a connected site, but it never explicitly ties that to the parameter or states the expected form (bare hostname vs. URL).

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 the resource precisely and enumerates its contents — conversion events and excluded paths, priority pages and sold services, confirmed competitors — so an agent knows exactly what record it is fetching. It stops short of differentiating from near-siblings such as webops_site_profile or webops_competitors, and it phrases the purpose as a noun phrase rather than an explicit verb, leaving the read action to be inferred.

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?

'Read by every finding and investigation' implies this is the foundational context call that other tools depend on, which is genuinely useful framing. However, there is no explicit when-to-use versus webops_site_profile or webops_competitors, and no when-not guidance beyond the not-found case.

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