Skip to main content
Glama
Sign In
Rivalize MCP Server

Rivalize MCP Server

by Downshift
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List tracked competitors (Agent plan)

list_agent_competitors
Read-onlyIdempotent

Lists tracked competitor slots on a Rivalize Agent plan, including last collection time, next refresh, and remaining monthly slot changes for managing who you monitor.

Instructions

List the competitor slots of your Rivalize Agent plan: who is tracked, when each was last collected, when it refreshes next, and how many slot changes are left this calendar month. Reading is free and calls no vendor. Only Agent plan keys use this; other plans use list_competitors.

Args: none.

Returns JSON: { data: { level, plan, slots_total, slots_used, refresh_days, slots: [{ slot, competitor: { id, name, url } | null, collection_status, last_collected_at, next_refresh_at, changes_left_this_month, changes_reset_at }] } }. Use competitor.id with get_agent_competitor.

Use when: "which competitors am I tracking?", "when does my data refresh?", "can I swap a competitor?".

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new behavioral facts: reading is free, no vendor call is made, and slot changes are quota-limited per calendar month with a reset timestamp. It stops short of describing error behavior for non-Agent keys, so it is not fully exhaustive.

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?

Front-loaded with purpose and plan scoping, then args, returns, and use-when — a clean structure. The inline JSON return shape is long but earns its place as a substitute for the absent output schema, though it could be trimmed of redundant nesting detail.

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 and no parameters, the description carries the full burden and does so: it documents the return envelope and per-slot fields, hands off the nested competitor.id to get_agent_competitor, and covers plan gating and quota semantics. An agent has everything needed to call and interpret it.

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?

Zero parameters, so the baseline is 4; "Args: none." correctly confirms the empty schema and prevents an agent from inventing filter arguments. Nothing further is needed.

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?

Specific verb + resource ("List the competitor slots of your Rivalize Agent plan") with the exact fields surfaced: who is tracked, last collection, next refresh, remaining slot changes. It explicitly separates itself from the sibling list_competitors by plan type, so an agent can pick between them 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 Guidelines5/5

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

Gives an explicit routing rule ("Only Agent plan keys use this; other plans use list_competitors") plus a "Use when" block with three concrete user phrasings. Both the when and the when-not are stated, not implied.

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

Deploy Server

Other Tools