Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

A website's goal

webops_goal
Read-onlyIdempotent

A connected website's goal (leads, sales, traffic or brand), or none. Findings are ranked by it. Another organization's or an unconnected site answers not found. Read-only.

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_goal"
  }
}

Input Schema

NameRequiredDescriptionDefault
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?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: which values can come back, that 'none' is a valid answer, that findings are ranked by the goal (downstream effect on other tools), and the not-found failure mode for foreign or unconnected sites. Only the exact response shape is left implicit.

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?

Four short sentences, zero filler, with the value enumeration and the ranking consequence front-loaded before the not-found caveat. Every sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, the description supplies everything needed: possible return values, the 'none' case, the not-found case, and the downstream significance of the goal. Nothing an agent needs in order to call it correctly is missing.

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 meaning. It conveys that the identifier is a connected website within the caller's organization and that an unconnected or foreign site yields not found, which partially compensates, but it never explicitly ties those constraints to the domain argument or gives format expectations.

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 the specific resource (a connected website's goal) and enumerates the exact possible values (leads, sales, traffic, brand, or none), which lets an agent distinguish it from the mutating sibling webops_set_goal. It never uses an explicit retrieval verb, but 'Read-only' plus the value list makes the operation unambiguous.

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 only implied: 'Read-only' and 'set' in the sibling name signal that changes belong elsewhere, but the description never explicitly says to use webops_set_goal for setting or when a goal lookup is warranted. It does give a clear when-not condition (another organization's or an unconnected site returns not found).

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