Skip to main content
Glama

ADS Beast

client_overview

Read-only

One client with its campaigns, key metrics and goals.

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

Input Schema

NameRequiredDescriptionDefault
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/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 safety is covered. The description's only added value is enumerating that campaigns, key metrics and goals come back in the payload, which matters because there is no output schema. It says nothing about what happens when client_id is unknown, whether data is cached or live, or how large the payload can get.

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?

One short sentence with no padding, which is efficient. But it is a noun phrase rather than a statement of action, and the terseness reads as under-specification for a tool that aggregates campaigns, metrics and goals rather than as disciplined brevity.

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?

With no output schema, the description is the only source of return-value information, and it gives just three nouns. For a composite overview tool with an undocumented identifier parameter and no annotations describing data freshness or scope, the definition does not give an agent enough to call it confidently or interpret what comes back.

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?

There is exactly one parameter, client_id, and schema description coverage is 0% — the schema only says it is an integer. The description never mentions client_id, so it does not compensate for the undocumented parameter. With a single unnamed-format identifier, saying 'client_id is the numeric client identifier' would have closed the gap.

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 fragment 'One client with its campaigns, key metrics and goals' does identify the resource (a single client) and signals that the response bundles related data. But it has no verb and no differentiation from siblings such as get_client or client_goals, which plausibly return overlapping subsets. An agent cannot tell from this text why it would pick client_overview over get_client.

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 exclusions, and no mention of any alternative tool. Given a sibling named get_client and several goal/metrics-focused siblings, the absence of routing guidance is a real gap rather than a minor omission.

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.