Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Refresh a website's data now

webops_refresh_now
Destructive

Refreshes every free source of one of the organization's connected websites now, in the background, inside the plan's refreshes a day and its cooldown. Refused while one runs. Nothing happens until the person confirms: this returns a summary and a code for tc_confirm.

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_refresh_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, non-idempotent) it discloses concrete behavior: background execution, quota and cooldown gating, refusal when one is already running, and a two-step confirmation flow where "Nothing happens until the person confirms." It also says the call returns a summary plus a code for tc_confirm, which is exactly the kind of side-effect detail an agent needs before invoking a destructive tool.

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 short sentences, front-loaded with the action and scope, then the constraints, then the confirmation gate. Some clauses are telegraphic ("Refused while one runs."), costing a touch of clarity, but nothing is redundant.

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 mutation tool with no output schema, this covers the essential concerns: scope, quota, background nature, refusal condition, and the return value's role in confirmation. It falls short only on what counts as a "free source" and how the returned tc_confirm code should be used.

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 0% and the single parameter `domain` is only constrained by pattern and length, with no description. The description implies the argument selects "one of the organization's connected websites," which adds a little meaning (it must be a connected site, not an arbitrary URL), but it never names the parameter or gives format expectations.

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 uses a specific verb and scoped resource: "Refreshes every free source of one of the organization's connected websites now." The word "free" and "now" distinguish it from reporting tools in the sibling list such as webops_limits or webops_website_status, but it never names a sibling or contrast case explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear operating conditions: runs in the background, must fit inside the plan's daily refresh count and cooldown, and is refused while another refresh is running. It also states the confirmation requirement. What is missing is direction to the sibling that reports plan limits or status when the agent wants to check quota before calling.

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