Skip to main content
Glama

RivalSweeper Signals

Upcoming events & recent activity

get_upcoming_events_news_and_activity
Read-onlyIdempotent

Your dashboard agenda: upcoming holidays and retail events in each brand's own market (e.g. Hanukkah for Israeli brands), with the brands each event is for, news mentions (7 days) and recent catalog activity per brand.

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

Input Schema

NameRequiredDescriptionDefault
domainsNoBrand domains from your RivalSweeper account, e.g. ["gymshark.com"]. Omit for all your tracked brands.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered by structured data. The description adds useful scope behavior beyond that: a hard 7-day window on news mentions and market-localized event selection. It does not describe data freshness for catalog activity, ordering, result volume, or behavior when a domain is untracked.

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?

A single dense sentence that front-loads the 'dashboard agenda' framing and then enumerates the payload sections in a readable order. It is slightly clause-heavy but every clause carries information about returned content.

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?

With no output schema, the description carries the burden of explaining what comes back, and it does so by naming events, associated brands, news mentions and catalog activity. For a one-parameter read-only aggregate this is largely sufficient; minor omissions are freshness/ordering and result-size expectations.

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 100% and the single 'domains' parameter is fully documented in the schema, including the omit-for-all-brands default, so the baseline is 3. The description does not reference the domains filter or add any semantics on top of what the schema already 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 enumerates the three resources returned — localized upcoming holidays/retail events, 7-day news mentions, and recent catalog activity per brand — which goes well beyond restating the name. It also clarifies a non-obvious scope rule: events are localized to each brand's own market (e.g. Hanukkah for Israeli brands). It stops short of explicitly distinguishing itself from siblings like get_competitor_moves_feed or get_newly_published_products_and_pages, which overlap in subject matter.

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

Usage Guidelines2/5

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

The phrase 'Your dashboard agenda' hints that this is an overview/landing tool, but there is no explicit statement of when to call it, when to prefer a narrower sibling, or any prerequisites. An agent must infer that this is a broad recap tool rather than a targeted feed.

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