Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Suggest one page's type now

webops_classify_page
Destructive

Suggests by AI the type of one crawled page the rules cannot type, now, spending one of the month's page suggestions (money). Returns the type with the page's own words that show it; a suggestion, never a rule's certainty. 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>",
      "page": "<page>"
    },
    "name": "webops_classify_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesAn address or a path of a crawled page.
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations, it discloses the most important hidden cost – it 'spends one of the month's page suggestions (money)' – and clarifies the confidence level ('a suggestion, never a rule's certainty') and that no change lands until a person confirms. That cost and irreversibility context is exactly what annotations cannot express, though it does not quantify quota or describe failure behavior when the quota is exhausted.

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 sentences, front-loaded with the action and scope, then cost, then the confirmation caveat – no filler. Phrasing like 'Suggests by AI' and the parenthetical '(money)' is slightly awkward but each sentence carries distinct information.

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?

With no output schema, the description does the work of explaining returns (the type, supporting page text, a summary, and a confirm code). The main residual gap is what happens on quota exhaustion or invalid page input, plus the undocumented domain parameter, but the call-and-follow-up path is otherwise clear.

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%: 'page' is documented in the schema and the description corroborates it as a crawled page address/path, but 'domain' is undocumented in both places. The description adds the useful constraint that the page must already be crawled, but does not compensate for the missing domain semantics or the relationship between domain and page.

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?

The description names a specific verb and resource ('Suggests by AI the type of one crawled page') and narrows the scope to pages 'the rules cannot type', which is a real differentiator from rule-based classification. It also frames the output as 'the type with the page's own words that show it', so an agent knows exactly what comes back.

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?

It states the precondition for use ('one crawled page the rules cannot type') and the confirmation workflow ('this returns a summary and a code for tc_confirm'), which tells the agent this is step one of a two-step flow. It stops short of naming a sibling to call instead when the page is already typed, so the exclusion side is only implied.

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