Skip to main content
Glama

IndustryLens

by com.industry-lens
OverviewDiscussionsAdmin

Get recent competitor pricing changes

get_pricing_changes

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

TableJSON 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.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return payload (change_type, severity, materiality score, summary, detection date), notes that the date is the 'real detection date', and states the coverage limit ('markets IndustryLens publicly tracks'). It omits auth/permission requirements, rate limits, and pagination behavior, so not a full 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-loaded with the usage trigger, then scoping, then return shape — a sensible order with no wasted sentences, though the closing 'No other public source exposes...' line is promotional rather than operational.

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?

No output schema exists, and the description compensates by describing the returned fields and their meaning, plus scope limits and default behavior. For a 4-parameter, zero-required read tool, an agent has everything needed to call it 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 the baseline is 3, but the description adds genuine meaning: it explains the scoping decision (pass `competitor` for one company, omit for a feed) and the batch semantics ('each in input order', with `since`/`limit` applying to every entry). That is real value beyond the schema text.

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+resource ('Returns structured pricing/packaging changes IndustryLens has detected') and enumerates the returned fields, making the scope concrete. It never names an alternative sibling (e.g. get_competitor_moves_diff or list_competitor_moves), so an agent must infer differentiation itself, which keeps it out of 5 territory.

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 clearly routes between the single `competitor` scope and the batched `competitors` scope. No exclusion criteria or when-not-to-use guidance is given, so it falls short of a 5.

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