Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Rankings over time

webops_rankings
Read-onlyIdempotent

The followed and pinned searches of a connected website: 12 weeks of weekly positions, the page ranking for each, the like-for-like trend, and exact ranks from lookups beside them. 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_rankings"
  }
}

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 closing 'Read-only' is largely redundant. The description does add real behavior the annotations do not: a fixed 12-week window of weekly data, inclusion of both followed/pinned search positions and separate lookup-derived exact ranks, and a defined not-found response for foreign or unconnected domains.

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 definition is a single front-loaded sentence that leads with the scope and contents, followed by the error condition, which is a sensible order. Some phrasing is dense ('exact ranks from lookups beside them') and the trailing 'Read-only' repeats the annotations rather than earning its 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?

With no output schema, the description usefully enumerates the shape of the return (weekly positions, ranking page, trend, lookup ranks). Combined with annotations covering the safety profile, an agent has enough to call it correctly; the only shortfall is the unexplained domain parameter.

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 required parameter with 0% schema description coverage, so the description must carry the meaning. It indirectly constrains it by saying the target must be a connected website and that unconnected sites answer not found, but it never states that the parameter is the website domain, nor any format expectations beyond what the schema pattern already enforces.

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 concretely states what is returned: 12 weeks of weekly positions for followed and pinned searches of a connected website, the ranking page per position, the trend, and lookup ranks. It is specific about the resource and the data window, but it never names the close sibling webops_rankings_compare, so an agent must infer the distinction from the name 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?

Usage is only implied: the reader learns this applies to 'a connected website' and that other organizations or unconnected sites yield not-found, which functions as a prerequisite. There is no explicit guidance on when to prefer this over webops_rankings_compare or the lookup-based siblings, and no stated exclusions.

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