Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Set the questions asked of AI assistants

webops_set_ai_questions
Destructive

Sets the questions asked of AI assistants for one of the organization's websites, one per line, inside the plan's limit. 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>",
      "questions": "<questions>"
    },
    "name": "webops_set_ai_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
questionsYesOne question per line; the set becomes exactly these.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is covered; the description still earns credit for disclosing the two-step confirm flow ("Nothing happens until the person confirms: this returns a summary and a code for tc_confirm") and the plan-limit constraint. It stops short of saying the existing question set is overwritten or what happens when the limit is exceeded.

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 mutation and its scope first, the deferred-confirmation behavior second. No filler or redundant restatement of the title.

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, two-parameter mutation with no output schema, the description supplies the key operational facts (scope, line format, plan limit, deferred commit, returned confirm code). The remaining gap is that the tc_confirm follow-up is referenced but never explained, leaving an agent unsure what to do with the returned code.

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%: the questions parameter is documented in the schema, and the description echoes the one-per-line format while adding the plan-limit validation rule not present in the schema. The domain parameter is only constrained by a regex pattern and gets no explanation of what a valid site identifier looks like; baseline 3 fits the partial coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Sets") plus the exact resource ("the questions asked of AI assistants") and scope ("for one of the organization's websites"). This clearly contrasts with the read-side sibling webops_ai_questions, so an agent can pick it without opening the schema.

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?

The description implies when to call it (configuring the question set for a site) and adds the important workflow cue that nothing is applied until confirmation. It does not name alternatives or state exclusions, e.g. that reading current questions requires webops_ai_questions or that a separate step carries out the change.

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