Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

How to investigate a question

webops_playbook
Read-onlyIdempotent

How to investigate a question: the playbook's steps, the tool each calls, how to read it, the fixed answer parts and rules (cite tool outputs; inside the noise band means nothing happened; "cannot tell" is valid). P0 when none matches. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "webops_playbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoP0–P6 or its kind (general, search_drop, visits_change, conversions_change, what_next, one_page, audience).
questionNoThe person's question; the playbook is chosen by its words (P0, the general method, when none matches).

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, and the description's 'Read-only.' merely restates that. What it does add is content-level behavior: fixed answer parts, the rule that inside the noise band means nothing happened, and that 'cannot tell' is a valid answer — genuinely useful context beyond the annotations, though return structure is only vaguely sketched.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence, but it is a comma-spliced enumeration of contents rather than a front-loaded statement of purpose, so the reader must parse the list to find out what the tool actually is. 'P0 when none matches' sits at the end, disconnected from the rest.

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?

For a two-parameter, no-output-schema guidance tool, the definition covers the essentials (fallback behavior, the noise-band rule, 'cannot tell' being valid) but never states what the response looks like or when in a workflow to call it. Adequate but with clear gaps for an agent deciding whether to call this first.

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 100%, and the schema itself already explains both `kind` (P0–P6 or kind name) and `question` (playbook chosen by its words, P0 fallback). The description adds nothing about parameter format or interaction, so the baseline 3 applies.

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

Purpose3/5

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

The title and description say it returns a playbook of investigation steps, but the phrasing is a list of contents rather than a verb+resource statement: 'the playbook's steps, the tool each calls, how to read it, the fixed answer parts and rules'. An agent can infer it is a procedural guide, but it cannot tell from the description alone how this differs from siblings like webops_investigations or webops_measurement.

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 implied rather than stated: the schema note says the playbook is chosen by the question's words, with P0 as the fallback when nothing matches. There is no explicit 'use this before calling the analysis tools' or when-not guidance, and no named alternative, so the agent must infer the routing role.

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