Skip to main content
Glama

IndustryLens

by com.industry-lens

Get the whole-category map for a market

get_market_landscape

Given a market (a vertical slug or name), return the published category overview plus every player IndustryLens tracks in that market — the whole-CATEGORY map, not a self-selected competitor set. Returns the hub (title, abstract, tldr, hero_stats, url), the deduped list of players (name, domain, business_model), and market_news — the latest weekly market summary (narrative, top topics, new entrants, topic momentum, source URLs). Returns { covered: false } for markets IndustryLens doesn't publicly track. Use list_markets to discover slugs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketYesA vertical slug (exact) or market name (ILIKE), e.g. 'sales-intelligence' or 'sales intelligence'.

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description bears the full burden. It discloses that the tool returns data from IndustryLens' tracking, including the edge case of { covered: false } for untracked markets. However, it does not explicitly state behavioral traits like read-only nature, authorization needs, or rate limits, which reduces transparency.

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?

Every sentence serves a purpose: input definition, output structure, edge case, and usage hint. The description is front-loaded with the core purpose and remains concise without unnecessary details.

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?

Despite no output schema, the description fully explains the return value structure and edge cases. It appropriately differentiates from sibling tools and references 'list_markets' for discovery. The complexity is low (single parameter), so the description is complete enough for an agent to decide.

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?

The schema coverage is 100% with a well-described parameter. The description adds value by explaining acceptable input formats (slug or name), providing examples, and hinting at ILIKE matching behavior. This goes beyond the schema's description to clarify usage.

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?

The description explicitly states it returns the whole-category map for a market, distinguishing it from a self-selected competitor set. It details the output structure and mentions the edge case of uncategorized markets. The purpose is clear and differentiates from sibling tools like 'find_competitors' and 'list_markets'.

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?

The description provides clear context for when to use this tool (to get the whole-category map, not a self-selected competitor set) and explicitly suggests using 'list_markets' to discover slugs. While it does not list explicit alternatives or when-not-to-use scenarios, the contrast implies other tools for specific competitor sets.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct aspect of competitive intelligence—competitor discovery, detailed comparisons, market landscapes, pricing changes, strategic moves, and reports—with no functional overlap. The descriptions clearly differentiate their purposes.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., find_competitors, get_comparison, list_markets), with verbs like 'find', 'get', 'list', and 'subscribe' appropriately chosen. No mixing of conventions.

Tool Count5/5

With 12 tools, the server is well-scoped for a competitive intelligence domain. Each tool serves a clear function, and the count is neither too small nor overwhelming for an agent to navigate.

Completeness5/5

The tool surface covers the full lifecycle: discovering competitors, obtaining profiles, comparing them, viewing market landscapes, tracking pricing and strategic moves, and accessing reports. There are no obvious missing operations for the stated purpose.

Resources