Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Set the competitors counted

webops_set_competitors
Destructive

Sets the competitors counted in AI share of voice for one of the organization's websites, one domain per line. 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>",
      "competitors": "<competitors>"
    },
    "name": "webops_set_competitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
competitorsYesOne domain 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 this as destructive and non-idempotent, and the description adds genuinely useful context beyond them: the write is staged, nothing is applied until a person confirms, and the call returns a summary plus a tc_confirm code. It does not explicitly warn that the existing competitor set is replaced wholesale, which is the main destructive consequence.

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

Conciseness5/5

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

Two tight sentences: the scope comes first, then the confirmation contract that governs how the tool must be called. No filler or restatement of the title.

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?

For a destructive two-parameter mutation with no output schema, the confirmation flow compensates well, but the description omits that the prior competitor list is discarded and points at a 'tc_confirm' step whose corresponding tool (likely webops_accept) is never named, leaving the agent to guess the follow-up.

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 50%, so the description must carry part of the load. It does clarify that the domain parameter is the organization's website and that competitors are supplied one domain per line, but it says nothing about validation, normalization, or a domain-count limit for the competitors string.

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 precisely scoped resource (competitors counted in AI share of voice for one organization website), which is enough to tell it apart from read-only siblings like webops_competitors. It stops short of explicitly contrasting itself with those siblings, so it sits just below the top.

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 implied: use this to define the competitor set for a site, one domain per line. There is no explicit statement of when not to use it, no mention of checking the current set first via webops_competitors, and no prerequisites beyond the confirmation note.

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