Skip to main content
Glama

Get my competitor gaps

get_competitor_gaps
Read-onlyIdempotent

Sites AI cites in answers that name a competitor but not the member's brand (Kliqo's Gap analysis), largest gaps first, with the prompts behind them. Pass domain to see the answers for one site. Use for "where are competitors winning?" or "which sites should mention us?". Needs sign-in to Kliqo (read-only).

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

Input Schema

NameRequiredDescriptionDefault
kindNodomains
limitNo
modelNoOnly this AI model's answers; leave out for the project's current models
rangeNoDate range, ending today in the project's time zone30d
domainNoOne site or URL from the list, to see its answers
projectNoProject name, domain or id; leave out for the workspace's current project
end_dateNoExact end date (YYYY-MM-DD), today at the latest
start_dateNoExact start date (YYYY-MM-DD), for example the 1st of a month; use with end_date instead of range

Output Schema

NameRequiredDescriptionDefault
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds two genuinely new facts: an authentication requirement ("Needs sign-in to Kliqo") and the default sort order (largest gaps first). It omits pagination/truncation behavior and what an empty result means, which keeps it off a 5.

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 tight sentences: what it returns, how to drill down, when to use it, plus an auth note. The core definition is front-loaded with zero filler. Slight density cost from the parenthetical branding ("Kliqo's Gap analysis") and the compressed subject of the first sentence.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The description supplies the essential conceptual model, sort order, auth need, and the one drill-down parameter. For an 8-optional-parameter tool it could still say more about scoping defaults (model/range/project) but nothing critical is missing.

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 description coverage is 75%, so most parameters (model, range, project, end_date, start_date, domain) are already documented in the schema, and the baseline of 3 applies. The description only adds meaning for `domain` (drill into one site's answers); `kind` and `limit` remain undocumented, and nothing is said about how range/start_date interact beyond what the schema states.

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 a specific, non-obvious resource: sites cited by AI answers that mention a competitor but not the member's brand, plus the ordering (largest gaps first). That is far more than a restatement of the name, and the gap concept distinguishes it from a plain source listing. It stops short of explicitly contrasting with siblings like get_top_sources or get_answers, so a sibling-level 5 is not earned.

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?

Two concrete user-intent phrasings ("where are competitors winning?" / "which sites should mention us?") tell the agent when this tool is the right pick, and "Pass domain to see the answers for one site" clarifies the drill-down mode. No exclusions or named alternatives are given, so the agent must infer when to reach for get_top_sources instead.

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.

Resources