list_marketsList the B2B SaaS markets (categories) IndustryLens monitors. Each item has a slug usable with get_market_landscape for the full category map. Ordered by name.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description adds structure info (slug, ordered by name) but does not explicitly state read-only nature or error behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with key action and resource, no unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters and no output schema, description covers purpose, output structure (slug), and next-step hint. Slightly lacks mention of potential limits or return format details.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters to describe; schema coverage is 100% trivially. Baseline for 0 params is 4.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses specific verb 'list' and resource 'markets', stating it lists B2B SaaS categories. It clearly distinguishes from sibling tools like get_market_landscape which is for full maps.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implies usage by mentioning slug usability with get_market_landscape, but no explicit when-to-use or when-not-to-use compared to alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.