Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Visibility in AI answers

webops_ai_visibility
Read-onlyIdempotent

Per confirmed question, the share of AI assistants' answers that cite or name the website, with 95% ranges, and the month's checks used. 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_ai_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already establish the read-only, idempotent, closed-world safety profile, so the description's trailing "Read-only" is redundant. What it does add beyond the structured data is genuinely useful: the metric definition, the presence of confidence ranges, the reporting window (month's checks used), and the exclusion of third-party or unconnected site answers. It does not describe granularity, pagination, or failure modes when no questions are confirmed.

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

Conciseness3/5

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

Only two sentences, and the metric definition is front-loaded, which is good. However, the second sentence ("Another organization's or an unconnected site answers not found") is grammatically broken and takes effort to parse, and closing with "Read-only" restates the readOnlyHint annotation rather than adding value.

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?

Given a one-parameter read metric with no output schema, the description does a reasonable job sketching what comes back: share, 95% ranges, and checks consumed. The gaps are the domain input convention and any indication of behavior when the site has no confirmed questions or no AI answers yet, which matter for an agent deciding whether the call is worthwhile.

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?

The sole parameter, domain, has zero schema description coverage, so the description must carry the burden and largely does not: it refers only to "the website" without clarifying format expectations such as whether to pass a bare hostname or full URL, or how subdomains are handled. The schema's pattern and length constraints are the only guidance, leaving an agent to guess the practical input convention.

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 metric rather than a vague action: the share of AI assistant answers that cite the site, broken down per confirmed question, with 95% ranges and checks used. It also states a scope boundary (answers from other organizations or unconnected sites are excluded), which helps separate it from the broader sibling tools. It stops short of naming any sibling explicitly, so an agent must infer the boundary from behavior alone.

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?

The phrase "per confirmed question" implies a prerequisite that AI questions must first be configured (plausibly via webops_set_ai_questions) before this returns anything, which is useful implied context. Beyond that there is no explicit when-to-use or when-not-to-use guidance, and no alternative is named for callers who want competitor or prompt-level data (webops_ai_competitors, webops_ai_questions, webops_run_ai_check).

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