Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Set a website's funnel steps

webops_set_funnel_steps
Destructive

Sets the person's own funnel steps for a website (read by the next refresh), or clears them to go back to the automatic funnel. Needs the person's approval. 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>",
      "steps": "<steps>"
    },
    "name": "webops_set_funnel_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsYes3 to 6 lines, one step each: visit, engaged, event <name>[, <name>], or page <path>[, <path>] (a path ending in * is a prefix). Empty: back to the automatic funnel.
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.9/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: a two-phase approval flow ('nothing happens until the person confirms'), a deferred effect ('read by the next refresh'), and a return shape ('a summary and a code for tc_confirm'). Given destructiveHint=true and idempotentHint=false are already declared, the remaining gaps are minor, e.g. what happens to a pending change that is never confirmed.

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 what changes and the revert option, then the approval gate. 'Needs the person's approval' and 'Nothing happens until the person confirms' overlap slightly, but the redundancy usefully emphasizes the blocking behavior.

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 destructive, non-idempotent mutation with no output schema, the description covers the effect, the deferral, the approval gate, and the return values. It leaves open what 'tc_confirm' refers to (a sibling tool such as webops_accept) and whether the domain must be an already-tracked website.

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?

The schema fully documents 'steps' (line grammar, 3-6 lines, empty means automatic) and the description adds the important 'read by the next refresh' timing, but 'domain' has no description in either place. With 50% schema coverage, the description does not compensate for the undocumented parameter beyond implying 'a website'.

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?

States a specific verb and resource ('Sets the person's own funnel steps for a website') and covers both modes, setting and clearing back to the automatic funnel. It does not name the read counterpart (webops_funnel_steps) or otherwise differentiate itself explicitly from siblings, so it stops short of a 5.

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?

Clear about when this applies: overriding the automatic funnel, or passing empty steps to revert to it. The confirmation prerequisite is stated plainly. No sibling alternative is named and there is no guidance on what to do if the person declines the approval.

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