Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Questions asked and what was missing

webops_investigations
Read-onlyIdempotent

A website's investigation log: question kinds no playbook covered, how often they ended in "cannot tell", what data was missing, feedback, and what repeats enough to propose as a playbook or data source. 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_investigations"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so 'Read-only' in the description is largely repetition. What the description does add is a picture of the aggregation behavior — that the log surfaces 'cannot tell' outcomes and recurring gaps worth promoting to a playbook or data source — which is genuine context beyond the annotations, but nothing is said about scope, time window, or result size.

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?

One sentence, front-loaded with the resource and then the contents, with no filler. The itemized middle clause is dense but every element describes a real part of the payload; the trailing 'Read-only' is the only wasted phrase.

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

Completeness3/5

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

With no output schema and no parameter documentation, the description carries a lot of weight. It does reasonably well at characterizing the returned content, but leaves the sole input parameter, the reporting window, and the result granularity unaddressed, which is thinner than an analysis-style aggregation tool warrants.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 burden. The phrase 'A website's investigation log' only weakly implies that 'domain' scopes the result to one site; it says nothing about accepted domain format or that the log covers only that property.

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?

The description names the specific resource — a website's investigation log — and enumerates its contents (uncovered question kinds, 'cannot tell' rates, missing data, feedback, repeat patterns). It is clear what data comes back, though there is no leading verb and no explicit differentiation from siblings such as webops_investigation_feedback or webops_ai_questions, which overlap with the 'feedback' and 'question kinds' content it lists.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no exclusions. An agent cannot tell from this text whether to call this tool or webops_investigation_feedback, webops_ai_questions, or webops_playbook, all of which sound adjacent to the described content.

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