Skip to main content
Glama
Sign In

Ripplewatch

by ai.ripplewatch
OverviewDiscussionsAdmin

List tracked competitors

list_competitors
Read-only

List every competitor this account tracks, oldest first, with name, domain and category. Call this first to get exact names before get_competitor. It returns no scores or signals (use get_momentum or get_briefing for those). An empty list means nothing is tracked yet, so suggest add_competitor. Read-only, no parameters.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare read-only behavior, but the description adds useful behavioral context: oldest-first ordering, absence of scores/signals, and the meaning of an empty result. It does not contradict the annotations.

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?

The description is short, front-loaded with the main purpose and return fields, and each sentence carries useful information about usage, exclusions, or empty-state handling.

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?

No output schema exists, so the description appropriately explains what is returned, ordering, what is not returned, and how to interpret an empty list. It is complete for a zero-parameter read-only list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, and the description explicitly states 'no parameters,' which is consistent with the empty schema. With no parameters to explain, the baseline is 4.

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 uses a specific verb (list) and resource (competitors tracked by the account), and it clearly distinguishes the tool from siblings like get_competitor, get_momentum, and get_briefing. It also specifies returned fields and ordering.

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

Usage Guidelines5/5

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

It explicitly says to call this first before get_competitor, routes score/signal needs to get_momentum or get_briefing, and tells the agent to suggest add_competitor when the list is empty. This covers when to use it and alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ripplewatch toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources