Skip to main content
Glama
Sign In

IndustryLens

by com.industry-lens
OverviewDiscussionsAdmin

List a competitor's recent moves

list_competitor_moves
Read-only

Use when the user asks what a specific competitor has recently done or changed. Returns recent tracked strategic moves for one competitor, newest-first — the existence of each shift plus a was→now summary and the real analysis date (never a fabricated date). Returns { covered: false } for companies IndustryLens doesn't publicly track, and an empty list for covered companies with no moves detected yet.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "competitor": "<competitor>"
    },
    "name": "list_competitor_moves"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax moves (default 10, max 50).
competitorYesCompetitor name or domain (e.g. 'Apollo' or 'apollo.io').

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only cover read-only and closed-world; the description adds substantial behavioral context beyond that: newest-first ordering, what each record contains (existence of the shift, was→now summary, real analysis date), a guarantee against fabricated dates, and two distinct empty-state semantics ('covered: false' vs. an empty list). That is exactly the kind of edge-case disclosure an agent needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with zero filler; the usage trigger is front-loaded, followed by return shape and then edge cases. Every clause carries information the agent would otherwise have to guess.

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, so the description must explain return values — and it does, covering ordering, per-record fields, and both empty-result variants. For a two-parameter read tool with read-only annotations, nothing material is missing.

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%, including the default/max for limit and the name-or-domain format for competitor, so the schema carries the parameter burden. The description reinforces the single-competitor framing but adds nothing about limit behavior or result truncation. Baseline 3 applies.

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 recent tracked strategic moves for one competitor') with explicit scoping to a single competitor and newest-first ordering. The singular-competitor scope cleanly separates it from siblings like get_competitor_moves_diff and get_comparison without needing the schemas.

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 what a specific competitor has recently done or changed.' That is clear usage context, but it offers no exclusions or named alternatives (e.g., pointing to find_competitors when the competitor is unidentified, or to the diff tool for comparisons).

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