Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Visits against conversions across pages

webops_patterns
Read-onlyIdempotent

How visits and conversions spread across a connected website's pages per channel (AI assistants, organic search). Too few pages: it says it cannot judge. 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_patterns"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD. Default: the 28 days ending on the latest day with data.
fromNoFirst day, YYYY-MM-DD. Default: the 28 days ending on the latest day with data.
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so 'Read-only' is redundant. The description does add genuine behavior beyond them: two distinct failure paths (insufficient page count yields an inability-to-judge response; foreign or unconnected domains return not found), which tells the agent how to interpret empty answers.

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 short, front-loaded sentences with no filler; the primary purpose leads and error behavior follows. Sentence fragments ("Too few pages: it says it cannot judge") are terse but unambiguous.

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 still conveys the unit of analysis (pages), the measures (visits, conversions), the segmentation (channel) and both error responses, which is most of what an agent needs. It does not describe the returned row shape or any page/row limits, leaving a modest gap.

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 67%, and the from/to parameters are already well documented in the schema with defaults. The description adds indirect meaning for domain by implying it must be a connected website whose pages are shared, but neither the channel dimension nor the date-window semantics are elaborated beyond the schema.

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 states a specific measure (visits and conversions) and its unit of analysis ('spread across a connected website's pages per channel'), with example channels given. It is clearly a page-level distribution tool, though it never names the closest sibling (webops_pages) to sharpen the boundary.

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 agent can infer this is for page-level distribution of visits/conversions by channel, and the failure modes ('too few pages', 'another organization's or an unconnected site') partly define when it applies. There is no explicit when-to-use versus webops_pages or webops_breakdown.

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