Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Ask AI assistants now

webops_run_ai_check
Destructive

Asks AI assistants the confirmed questions of one of the organization's websites now, in the background, inside the month's allowance (it spends money). Refused while a check runs or when the month's checks are used. 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_run_ai_check"
  }
}

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?

Adds substantial context beyond the annotations: the run spends real money against a monthly allowance, executes asynchronously in the background, can be refused for two distinct reasons, and only proceeds after confirmation. It also discloses the return payload (a summary plus a confirm code), which the annotations do not cover.

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 tight sentences, front-loaded with the action and followed by refusal conditions and the confirmation caveat. The parenthetical '(it spends money)' is terse but earns its place; a little more structure around the confirm flow would help, but there is no filler.

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?

Covers what an agent needs for a one-parameter, no-output-schema tool: cost implications, execution mode, refusal conditions, and the confirmation handoff. The only gap is that it never explains what the confirm code is used for or names the tool that consumes it.

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 description coverage is 0% for the single required 'domain' parameter, so the description must carry the meaning. 'One of the organization's websites' identifies what the argument represents, but it does not state that the value is a bare domain string matching a pattern, nor what happens if the site is not in the organization.

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: asks AI assistants the organization's confirmed questions for one website, now and in the background. It implicitly separates itself from the question-management siblings ('confirmed questions' means questions must already exist), but never names those siblings 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?

Gives concrete use conditions and prohibitions: refused while a check is already running or when the month's checks are used, and it requires human confirmation before anything happens. It lacks an explicit statement of when to prefer a sibling tool, but the preconditions are clear enough to route correctly.

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