Skip to main content
Glama
Sign In
Lexicon Intelligence

Lexicon Intelligence

by nadine302324-commits
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

lexicon_feed

Retrieve competitive intelligence for any market or industry, including recent developments, new entrant signals, and trend analysis.

Instructions

Competitive intelligence feed for a market or industry. Returns recent developments, entrant signals, and trend analysis.

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": {
      "industry": "<industry>"
    },
    "name": "lexicon_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryYesMarket or industry name
limitNoMaximum items to return (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided; description does not disclose whether the tool is read-only, has rate limits, or any side effects. Only states it 'returns' data, implying a safe operation but lacking explicit behavioral details.

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?

Two sentences, succinct and to the point. Efficiently conveys purpose and return type without extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Description covers overall purpose and return value type but lacks details on pagination, ordering, or item structure. Given simplicity and no output schema, it's minimally adequate but not fully complete.

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?

Input schema covers both parameters with descriptions (100% coverage). The tool description adds context on the return value (recent developments, etc.) but does not enhance parameter meaning beyond what the schema provides.

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 it returns a competitive intelligence feed with recent developments, entrant signals, and trend analysis. It distinguishes from sibling tools like compare and monitor.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool instead of alternatives like lexicon_compare or lexicon_monitor. Does not mention context or exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools