Skip to main content
Glama

ADS Beast

client_market_analysis

Read-only

The stored market analysis of a client: summary, competitor matrix, audience signals and the draft campaign strategy.

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_market_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNoall, summary, competitors, audience, strategy or insights.
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 the safety profile is covered and the bar is lower. The description adds the useful signal that the data is 'stored' (i.e., persisted and potentially stale), but it never says how fresh it is, whether a missing analysis returns empty or an error, or how large the payload is. For an open-world read tool this leaves real behavioral gaps.

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 resource and then enumerates contents. There is no filler and nothing redundant.

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 simple two-parameter read tool with annotations covering safety, the definition is close to adequate. It still omits the missing-data behavior, staleness, and two enum values ('all', 'insights'), which matter for calling it correctly on first try.

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 50%: the section enum is documented in the schema, but client_id has no description anywhere. The description's list of contents partially maps to the enum values but omits 'insights' and never mentions 'all', so it does not fully compensate for the undocumented required parameter.

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 precisely and enumerates its contents (summary, competitor matrix, audience signals, draft campaign strategy). The word 'stored' distinguishes it from the sibling client_market_analysis_run, which implies a fresh run, though the distinction is left implicit rather than stated. It is a noun phrase with no explicit retrieval verb, but the intent is unambiguous.

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?

'Stored' hints that this returns existing analysis rather than triggering a new one, which is the key routing decision against client_market_analysis_run. However, it never states when to prefer this over running a new analysis, nor what to do if no analysis has been generated yet. Usage is implied rather than directed.

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.