Skip to main content
Glama

ADS Beast

analytics_forecast_warnings

Read-only

Campaigns expected to break a KPI target within days, from a linear trend.

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": {
      "client_id": "<client_id>"
    },
    "name": "analytics_forecast_warnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that — the projection is a linear trend, implying a heuristic estimate rather than a guarantee — but says nothing about the forecast horizon, the KPI target source, or minimum data requirements.

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?

A single front-loaded clause with zero filler; the identifying information comes first. The fragmentary phrasing ('Campaigns expected to...') leaves the action implicit, but nothing is padded or redundant.

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

Completeness2/5

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

For a forecasting tool with no output schema, no parameter documentation, and an undefined threshold concept ('KPI target'), the definition is too thin — the agent cannot tell what fields come back, how 'within days' is bounded, or where the target is configured.

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% and the description says nothing about the single parameter, client_id. The name makes its meaning largely self-evident, but the description adds no scoping detail (whether it is required, whether results are restricted to that client) that the schema does not already supply.

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 resource concretely ('Campaigns expected to break a KPI target within days') and states the method ('from a linear trend'), so an agent knows this returns at-risk campaigns rather than raw forecasts. It does not, however, distinguish itself from the closely named sibling analytics_forecast or from analytics_kpi_health.

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, no exclusion conditions, and no named alternative such as analytics_forecast or analytics_kpi_health. The agent must infer from the phrase 'within days' alone when this tool is the right choice.

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.