Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Who ranks above us, now and then

webops_competitors
Read-onlyIdempotent

Who ranks above us, now and then, from stored lookups: per search our exact rank, the sites above, and new entrants, sites gone and result types gained or lost between lookups. Says when a search was never looked up. Never spends one. 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_competitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD (default: today).
fromNoFirst day, YYYY-MM-DD (default: 90 days ago).
queryNoOne search (default: every search looked up).
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 readOnly, idempotent, non-destructive and closed-world, so the description's added value is the provenance and freshness model: results come from previously stored lookups rather than a live fetch, and the output is a diff between lookups. 'Never spends one' is a concrete cost guarantee an agent cannot get from the annotations, and 'Says when a search was never looked up' discloses a partial-coverage behavior. It stops short of stating staleness bounds or how many lookups are compared.

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?

Three tight sentences, payload description front-loaded before the cost and coverage caveats. The telegraphic fragments ('Never spends one. Read-only.') are efficient but push toward ambiguity rather than crispness.

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 shape and does so well by listing rank, sites above, entrants, departures and result-type deltas. For a read-only, four-parameter tool the remaining gaps are the undocumented required 'domain' and the default date window, both of which an agent needs to call it correctly.

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 75%, and the one undocumented parameter is the required 'domain', which the description never mentions or explains. 'Per search' gestures at the query filter and 'between lookups' implies the from/to window, but the defaults (today, 90 days ago) and the all-searches default are left entirely to the schema. With coverage this high, the schema is doing the heavy lifting and the description adds only marginal meaning.

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 concretely (competitor rankings above us per search) and enumerates the payload: exact rank, sites above, new entrants, sites gone, result types gained or lost. It separates itself from the live-lookup siblings implicitly via 'from stored lookups ... Never spends one', though it never names webops_look_up_search or webops_ai_competitors directly.

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: 'from stored lookups' and 'Never spends one' tell the agent this is the no-cost path, so a fresh-data need must go elsewhere, but no alternative tool is named and no explicit when-not condition is given. 'Says when a search was never looked up' hints at a prerequisite gap the agent must handle, without saying what to do about it.

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