Skip to main content
Glama

ADS Beast

client_market_analysis_run

Read-only

Crawl the client's site, find and analyse competitors and build a market intelligence report. Takes minutes; read the result with client_market_analysis. AI: 1 AI request.

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

Input Schema

NameRequiredDescriptionDefault
forceNotrue re-runs even when a fresh report exists.
client_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations establish read-only, non-destructive, open-world behavior, and the description adds traits annotations cannot convey: the operation takes minutes and consumes one AI request (a cost/latency signal an agent should plan around). The mentions of crawling an external site align with openWorldHint=true, and nothing contradicts readOnlyHint=true.

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 compact clauses with the action front-loaded and the follow-up read stated second, no filler. The trailing 'AI: 1 AI request' tag is terse enough to be slightly cryptic, but it earns its place as a cost warning.

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

Completeness5/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 correctly tells the agent where the result lives (client_market_analysis) and how long to expect to wait, which is exactly what is missing otherwise. For a two-parameter, long-running job, an agent has what it needs to call this and then retrieve the result.

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%: force is documented, client_id is not. The description adds nothing about either parameter, not even that force controls re-running, so it neither compensates for the gap nor overrides the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names concrete verbs and resources: crawl the client's site, analyse competitors, build a market intelligence report. It also distinguishes itself from the sibling read tool by stating 'read the result with client_market_analysis', so an agent can tell the generate/read pair apart without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context for invocation and, crucially, routes the agent to client_market_analysis for retrieving output. It doesn't say when NOT to run this (e.g., when a fresh report already exists and force is false), though the schema's force description partly compensates.

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.