Skip to main content
Glama
Downshift

Rivalize MCP Server

by Downshift
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List tracked competitors

list_competitors
Read-onlyIdempotent

Lists competitors tracked in your Rivalize account, with optional project filter and pagination for reviewing who you track.

Instructions

List the competitors tracked in YOUR Rivalize account (tenant-isolated). Answers "which competitors am I tracking?".

Args:

  • project_id (string, optional): only one project's competitors. Call list_projects first for the id.

  • limit (number, optional): page size 1-100

  • offset (number, optional): pagination offset (default 0)

Returns JSON: { data: Competitor[], pagination: { total, limit, offset, returned, next_offset } }. Each Competitor includes id, project_id, project_name, name, website, threat_level, momentum_score, and brief where the server provides it. Keep paging with offset = pagination.next_offset until it is null.

momentum_score is the rival's momentum score, and threat_level is only that score's band (critical, high, medium, low, or unknown when there is no score): it is not a second assessment, so do not rank by it.

brief, when present, is how the rival stands as your workspace's Brief shows it: brief.standing is "ahead" (the rival is ahead of you), "behind", "even" or "no_read"; brief.standing_label is the Brief's own words; brief.as_of is the date of the report it was read from; brief.state is "read", "not_in_run" (no finished report covered this rival), "no_run", "unreadable" or "deferred" (still being read: the tool asks again a few times before it answers, so a row still "deferred" means call again in a moment).

To pick the "top" or biggest competitor: rank by brief.standing when present ("ahead" first, then "even", then "behind"), otherwise by momentum_score; break ties by highest momentum_score. A rival whose brief.state is not "read" has no standing yet: say so rather than ranking it by standing.

With a competitor's id: get_competitor_intelligence (its latest intelligence), get_battlecard (sales battlecard), get_evidence with its project_id (the sources behind its facts). For what a report said about it: list_reports for the project, then get_report with competitor set to its name. For when it was last observed: get_freshness for its project.

Use when: "which competitors am I tracking?", "who is my top competitor?", or before any per-competitor read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoPage size (1-100)
offsetNoPagination offset
project_idNoFilter competitors to this project (UUID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds genuinely new behavioral context beyond them — tenant isolation, the pagination protocol (offset = next_offset until null), the 'deferred' state that causes the tool to retry before answering, and the fact that threat_level is a band of momentum_score rather than an independent assessment.

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?

Well organized under Args/Returns/Use when headings and front-loaded with the core purpose, but it is long for a list tool and the brief.state enumeration is heavy detail for this surface. Some text (limit 'page size 1-100') duplicates the schema verbatim, and the decisive 'Use when' block sits last rather than up front.

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?

There is no output schema, so the description must carry the return contract, and it does: full JSON shape, the fields each Competitor carries, and how to page through results. It also pre-empts the trickiest ambiguity — how to compute a 'top' competitor and what to do when brief.state is not 'read'. Complete for the tool's call pattern.

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?

Schema coverage is 100%, so baseline is 3. The description still adds meaning: project_id is not just a filter but requires calling list_projects first for the id, and offset carries an implicit default of 0. The limit text merely restates the schema's '1-100', so the gain is modest but real.

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?

Opens with a specific verb and resource plus a scope qualifier: 'List the competitors tracked in YOUR Rivalize account (tenant-isolated)', and frames the question it answers. This cleanly separates it from sibling list_universe_companies, which covers a different (untracked) population.

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?

Ends with an explicit trigger list ('which competitors am I tracking?', 'who is my top competitor?', 'before any per-competitor read') and routes to specific siblings by scenario: get_competitor_intelligence, get_battlecard, get_evidence, list_reports/get_report, get_freshness. Nothing is left to inference.

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