Skip to main content
Glama
Sign In

IndustryLens

by com.industry-lens
OverviewDiscussionsAdmin

Get recent competitor pricing changes

get_pricing_changes
Read-only

Use when the user asks about a competitor's pricing/packaging changes, or wants a recent pricing-change feed. Returns structured pricing/packaging changes IndustryLens has detected — each with a change_type, severity, materiality score, a plain-language summary, and the real detection date. Pass a competitor (name or domain) to scope to one company, or omit it for a recent pricing feed. Pass competitors (up to 10 names/domains) instead to get a feed per company in one call, each in input order. The feed spans the markets IndustryLens publicly tracks. No other public source exposes structured competitor pricing-diffs like this.

Input Schema

NameRequiredDescriptionDefault
limitNoMax changes (default 20, max 50).
sinceNoISO date lower bound for detection (e.g. '2026-01-01'). Defaults to 90 days ago.
competitorNoCompetitor name or domain (e.g. 'Apollo' or 'apollo.io'). Omit for a market-wide recent pricing feed.
competitorsNoBatch alternative to `competitor`: up to 10 competitor names or domains. Omit `competitor` when using this. Returns one pricing 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 / competitors
      Added value: +{
+  "description": "Batch alternative to `competitor`: up to 10 competitor names or domains. Omit `competitor` when using this. Returns one pricing 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/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false; the description adds real value on top by enumerating the returned fields and disclosing the coverage limit ('spans the markets IndustryLens publicly tracks') and the source of truth (changes 'IndustryLens has detected'). It does not mention detection lag or data refresh cadence, which would matter for a 'recent changes' feed.

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?

Use condition is front-loaded and the three calling modes are covered compactly. The closing sentence ('No other public source exposes structured competitor pricing-diffs like this') is marketing boilerplate that does not help an agent decide or invoke.

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?

There is no output schema, and the description compensates by listing the return fields and the shape of the batch response. Coverage limits are disclosed. Minor gap: nothing describes how far back the dataset actually goes or whether results are paginated beyond `limit`.

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 already 100%, so the baseline is 3; the description earns a bump by clarifying the mutually exclusive semantics of `competitor` vs `competitors` and by noting one feed per company returned in input order with `since`/`limit` applied to each entry. Most of that restates the schema, but the exclusivity and ordering emphasis is useful for a batch call.

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?

States a specific verb and resource — returns structured pricing/packaging changes with change_type, severity, materiality score, summary, and detection date — so an agent knows exactly what it gets back. It stops short of naming a sibling (e.g. get_competitor_moves_diff) to draw the boundary against, leaving that differentiation implicit.

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?

Opens with an explicit trigger ('Use when the user asks about a competitor's pricing/packaging changes, or wants a recent pricing-change feed') and then routes between the three calling modes: single competitor, market-wide feed, or batch list. No when-not-to-use condition or named alternative tool is given, so the sibling boundary remains unstated.

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