Skip to main content
Glama

IndustryLens

by com.industry-lens

List IndustryLens intelligence reports

list_reports

Browse published competitive-intelligence reports. Filter by industry or target_role; results are ordered newest-first. Each returned item has a slug usable with get_report. URLs follow https://industry-lens.com/reports/.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10, max 50).
industryNoIndustry filter, ILIKE match (e.g. 'hr tech', 'devops', 'fintech').
target_roleNoTarget role filter, ILIKE match (e.g. 'marketing', 'sales', 'product').

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses ordering, filtering, and relation to get_report, but omits details on authentication, rate limits, or potential pagination beyond limit parameter.

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?

Two sentences with no waste; purpose is front-loaded, and every sentence adds value (filtering, ordering, slug usage, URL format).

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?

For a simple list tool with 3 optional params and no output schema, the description fully covers purpose, filtering, ordering, and integration with get_report, making it complete for agent use.

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%, so baseline is 3. The description adds minor value by stating filtering purpose, but does not provide new details beyond schema descriptions.

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 clearly states 'Browse published competitive-intelligence reports' with verb 'browse' and resource 'reports', and distinguishes from sibling tools like get_report by mentioning returned slugs are usable with that tool.

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?

It provides context on filtering and ordering, and implies usage for listing vs. get_report for retrieval, but does not explicitly state when not to use or alternatives among siblings.

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