Skip to main content
Glama

ADS Beast

competitor_aeo_benchmark

Read-only

Compares how often AI models mention the client versus competitors for the same prompts. 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": "competitor_aeo_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idYes
competitorsNoCompetitor names or domains.

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?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value with 'AI: 1 AI request', which signals cost and that results depend on live model output, but it does not disclose variability, prompt sourcing, or result shape.

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?

Two compact sentences with the core comparison front-loaded and the cost note trailing. Nothing is padded, though the terse 'AI: 1 AI request' fragment could be phrased more clearly.

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 two-parameter read-only tool with no output schema, the agent still lacks information on which prompts or models are used, how many competitors are accepted, and what the comparison output looks like. The cost line helps, but coverage is only adequate.

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 competitors array is described in the schema, while client_id is an undocumented integer. The description maps both parameters onto the client-versus-competitors concept but adds no format, count, or ID-type detail to compensate for the undocumented client_id.

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 states a specific verb and resource: comparing how often AI models mention the client versus competitors for the same prompts. That is clearly distinct from a single-brand visibility scan, though it never names a sibling to route against.

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 explicit when-to-use or when-not-to-use guidance and no named alternative such as aeo_visibility_scan or competitor_list. Usage is only implied by the phrase 'versus competitors for the same prompts'.

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.