Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Set the priority pages and services

webops_set_priorities
Destructive

Sets the pages that matter most on one of the organization's websites and the services they sell, inside the plan's limits. Findings on a priority page rank higher. 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>",
      "pages": "<pages>",
      "services": "<services>"
    },
    "name": "webops_set_priorities"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesYesOne page per line, an address or a path, optionally followed by ' | service'; the set becomes exactly these.
domainYes
servicesYesOne service the website sells per line; the set becomes exactly these.

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 flag destructiveHint=true and readOnlyHint=false, but the description adds genuinely new behavior: a plan-limit cap on what can be set, lower-than-expected no-op until human confirmation, and a return of a summary plus a tc_confirm code. It stops short of saying that existing priority pages/services are replaced or discarded, which is the main destructive consequence an agent needs to warn about.

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?

Four short sentences with the core action first, then the ranking effect, then the confirmation gate — well front-loaded and free of filler. The clause 'this returns a summary and a code for tc_confirm' is slightly compressed but still readable.

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 three-parameter mutation with annotations present and no output schema, the definition covers the effect on findings, the plan-limit constraint, the confirmation workflow, and the shape of the response. The remaining gap is the absence of any statement about overwriting prior priorities or what a plan-limit rejection looks like.

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?

Three parameters with 67% schema description coverage, so the schema already explains the line-delimited pages/services format and the ' | service' syntax. The description adds only that the total must stay within plan limits; it says nothing about domain selection beyond 'one of the organization's websites', even though that parameter has no schema description at all.

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 verb (sets) and a specific resource pair (priority pages and the services they sell) on one of the organization's websites, which cleanly separates it from read-only siblings like webops_pages or list_priced_services. It does not explicitly name a competing setter (e.g. webops_set_ranking_pins), so sibling differentiation is only implicit.

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?

It supplies real preconditions — the set must fit 'the plan's limits' and 'nothing happens until the person confirms' — which tells the agent this is a two-step, human-gated operation. It never states when to prefer this over adjacent setters such as webops_set_ranking_pins or webops_accept, so usage is implied rather than routed.

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