Skip to main content
Glama

Visibility Genies

Find competitor suggestions

find_saved_competitor_suggestions

Find suggestions from saved evidence only. Saves suggestions without accepting them. Follow returned coverage and cursor until complete; ignored rivals stay ignored. No provider calls or credits.

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": {
      "projectId": "<projectId>"
    },
    "name": "find_saved_competitor_suggestions"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
marketNo
statusNo
aiRangeNo
projectIdYes

Output Schema

NameRequiredDescriptionDefault
metaNo
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description adds genuinely new behavior: it persists suggestions without accepting them, it makes no provider calls and burns no credits, ignored rivals remain ignored across runs, and completion requires following coverage plus cursor. It stops short of saying whether re-running is idempotent or what 'saved evidence' must already exist.

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?

Four short, front-loaded sentences with essentially no filler; the scope constraint and the save-without-accept side effect come first. Minor looseness in 'Follow returned coverage', which reads as jargon without definition.

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?

An output schema exists, so return values need no explanation, but the tool is complex: five parameters, two nested objects, an enum filter, and pagination, with zero schema descriptions. The definition never explains what market, aiRange, or status select, so an agent would be guessing at most of its inputs.

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?

Five parameters with 0% schema description coverage and two nested objects (market, aiRange) plus a status enum, and the description explains none of them. The cursor is only mentioned as something returned to follow, and status is only obliquely touched by 'ignored rivals stay ignored' — the market and aiRange fields are entirely undocumented.

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?

States a specific verb and resource ("Find suggestions from saved evidence only") and immediately adds the non-obvious side effect that it saves suggestions without accepting them. 'Saved evidence only' implicitly distinguishes it from the live-data finders in the sibling set, though it never names one.

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?

"Follow returned coverage and cursor until complete" is real pagination guidance and "No provider calls or credits" tells the agent this path is free of credit cost, which implies when to prefer it. But there is no explicit when-to-use vs the live find_* competitors tools and no prerequisites stated.

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