Skip to main content
Glama

ADS Beast

analytics_kpi_health

Read-only

Quick status of all active campaigns: how many are on target and how many need attention.

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": "analytics_kpi_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered elsewhere. The description adds value by revealing the return shape is aggregate counts rather than per-campaign detail, but it says nothing about scope boundaries (does it aggregate across clients?), latency, or what 'needs attention' means operationally.

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

Conciseness5/5

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

A single sentence that front-loads the scope ('all active campaigns') and then the two quantities returned. Nothing is wasted and there is no filler.

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, the description usefully characterizes the result as two counts, and for a one-parameter read-only tool that is close to sufficient. The gap is the undocumented client_id and the undefined 'on target' threshold, which an agent would need in order to interpret or scope the call correctly.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter, client_id, with 0% schema description coverage, and the description never mentions it. An agent cannot tell whether passing client_id narrows the campaign set, or whether omitting it aggregates across all clients — a meaningful behavioral difference for an open-world multi-client analytics tool.

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?

States a concrete verb-and-resource pair: status over 'all active campaigns', returning counts of on-target vs. needs-attention. An agent knows what it gets back. It stops short of 5 because it never distinguishes itself from the near-identical sibling 'audit_campaign_health', leaving the agent to guess which health check to call.

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?

The word 'Quick' implies a lightweight summary versus a deeper diagnostic, which hints at when to prefer this tool. However, no alternative is named and no condition for when-not-to-use is given, so the routing decision is left to inference from sibling names alone.

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.