Skip to main content
Glama

IndustryLens

by com.industry-lens
OverviewDiscussionsAdmin

Get a competitor's dated change feed

get_competitor_moves_diff

Use when the user asks what changed, what's new, or wants a timeline of a competitor's moves. Returns the dated CHANGE-FEED for one competitor: every real was→now strategic shift IndustryLens detected, newest-first, each stamped with its real analysis date (never a fabricated date) — optionally since a given date. Input a domain or name. Returns { covered: false } with a CTA for companies not publicly tracked. Pass companies (up to 10 names/domains) instead of domain/name to get a change feed for several competitors in one call — each gets its own result block, in the order given.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoCompany name (e.g. 'Apollo'). Used when no domain is given.
limitNoMax moves (default 20, max 50).
sinceNoOptional ISO date (YYYY-MM-DD). Only moves analyzed on/after this date are returned.
domainNoCompany domain or homepage URL (e.g. 'apollo.io'). Preferred — most precise.
companiesNoBatch alternative to domain/name: up to 10 company names or domains. Omit domain/name when using this. Returns one change feed per entry, in input order; `since`/`limit` apply to every entry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / companies
      Added value: +{
+  "description": "Batch alternative to domain/name: up to 10 company names or domains. Omit domain/name when using this. Returns one change feed per entry, in input order; `since`/`limit` apply to every entry.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 10,
+  "minItems": 1,
+  "type": "array"
+}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses ordering (newest-first), date fidelity (real analysis dates, never fabricated), the { covered: false } fallback with a CTA, and batch semantics — substantial behavioral context. It omits auth/permission needs and any rate limits, keeping it short of a 5.

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-loads the trigger condition then details the return shape and batching. Dense with em-dashes and parentheticals, and the 'never a fabricated date' clause leans promotional, but each sentence conveys usable information.

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 and five parameters, the description supplies the return shape, the covered:false case, and the batch/multi-competitor behavior. It stops short of describing the individual move fields, but is otherwise sufficient to call the tool correctly.

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, but the description adds real meaning: domain/name selection guidance, and the batch contract for `companies` (per-entry result blocks, input order preserved, since/limit applied to every entry). That goes beyond what the schema states.

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?

States a specific verb and resource: returns the dated was→now change feed for one competitor, newest-first. It is clearly distinguishable from siblings like get_pricing_changes and list_competitor_moves by scoping to detected strategic shifts with real analysis dates.

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

Usage Guidelines4/5

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

Gives explicit trigger conditions ('when the user asks what changed, what's new, or wants a timeline'). It does not name sibling alternatives (e.g., against get_pricing_changes or list_competitor_moves), so routing is implied rather than fully specified.

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

All IndustryLens 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