Skip to main content
Glama
nadine302324-commits

Lexicon Intelligence

lexicon_compare_methodology

Analyze a single vendor across Political, Economic, Social, Technical, Legal, and Environmental factors with live source citations.

Instructions

Deep PESTLE Triangulation research on a single vendor. Returns structured Political, Economic, Social, Technical, Legal, Environmental analysis with live source citations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vendorYesVendor or company name
industryNoIndustry context
focusNoOptional focus area within PESTLE

Implementation Reference

  • Input schema definition for lexicon_compare_methodology tool. Defines vendor (required), industry (optional), and focus (optional) parameters.
    {
      name: "lexicon_compare_methodology",
      description: "Deep PESTLE Triangulation research on a single vendor. Returns structured Political, Economic, Social, Technical, Legal, Environmental analysis with live source citations.",
      inputSchema: {
        type: "object",
        properties: {
          vendor:   { type: "string", description: "Vendor or company name" },
          industry: { type: "string", description: "Industry context" },
          focus:    { type: "string", description: "Optional focus area within PESTLE" },
        },
        required: ["vendor"],
      },
    },
  • index.js:85-92 (registration)
    Registration mapping that maps 'lexicon_compare_methodology' to the remote API method 'lexicon.compare.methodology'.
    const TOOL_MAP = {
      lexicon_compare_vs:          "lexicon.compare.vs",
      lexicon_compare_methodology: "lexicon.compare.methodology",
      lexicon_compare_topic:       "lexicon.compare.topic",
      lexicon_monitor_outage:      "lexicon.monitor.outage",
      lexicon_monitor_refunds:     "lexicon.monitor.refunds",
      lexicon_feed:                "lexicon.feed",
    };
  • Generic CallToolRequestSchema handler that proxies all tool calls to the remote Lexicon API. For lexicon_compare_methodology, it maps to remote tool 'lexicon.compare.methodology' via TOOL_MAP.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
      const remoteTool = TOOL_MAP[name];
      if (!remoteTool) {
        return { content: [{ type: "text", text: `Unknown tool: ${name}` }], isError: true };
      }
    
      const headers = { "Content-Type": "application/json" };
      if (API_KEY) headers["X-API-Key"] = API_KEY;
    
      const response = await fetch(`${BASE_URL}/mcp/v1`, {
        method: "POST",
        headers,
        body: JSON.stringify({
          jsonrpc: "2.0",
          id: 1,
          method: "tools/call",
          params: { name: remoteTool, arguments: args },
        }),
      });
    
      const data = await response.json();
      if (data.result) return data.result;
      return {
        content: [{ type: "text", text: JSON.stringify(data.error || data) }],
        isError: true,
      };
    });
  • index.js:9-83 (registration)
    Full TOOLS array listing all available tools; lexicon_compare_methodology is defined at index position 2 (lines 23-35).
    const TOOLS = [
      {
        name: "lexicon_compare_vs",
        description: "Head-to-Head VS comparison between two vendors or products. Retrieves live evidence from 20 independent web sources and applies PESTLE Triangulation to produce a structured comparison report.",
        inputSchema: {
          type: "object",
          properties: {
            vendorA:  { type: "string", description: "First vendor or product name" },
            vendorB:  { type: "string", description: "Second vendor or product name" },
            industry: { type: "string", description: "Industry context (e.g. fintech, healthcare, SaaS)" },
          },
          required: ["vendorA", "vendorB"],
        },
      },
      {
        name: "lexicon_compare_methodology",
        description: "Deep PESTLE Triangulation research on a single vendor. Returns structured Political, Economic, Social, Technical, Legal, Environmental analysis with live source citations.",
        inputSchema: {
          type: "object",
          properties: {
            vendor:   { type: "string", description: "Vendor or company name" },
            industry: { type: "string", description: "Industry context" },
            focus:    { type: "string", description: "Optional focus area within PESTLE" },
          },
          required: ["vendor"],
        },
      },
      {
        name: "lexicon_compare_topic",
        description: "Topic-specific competitive intelligence. Ask any comparison question across vendors, markets, or features.",
        inputSchema: {
          type: "object",
          properties: {
            topic:    { type: "string", description: "The comparison topic or question" },
            industry: { type: "string", description: "Industry context" },
          },
          required: ["topic"],
        },
      },
      {
        name: "lexicon_monitor_outage",
        description: "Live outage and reliability monitoring for a vendor. Returns current status, recent incidents, and reliability signals from independent sources.",
        inputSchema: {
          type: "object",
          properties: {
            vendor: { type: "string", description: "Vendor name to check for outages" },
          },
          required: ["vendor"],
        },
      },
      {
        name: "lexicon_monitor_refunds",
        description: "Refund rate and customer satisfaction signal monitoring for a vendor.",
        inputSchema: {
          type: "object",
          properties: {
            vendor:   { type: "string", description: "Vendor name" },
            industry: { type: "string", description: "Industry context" },
          },
          required: ["vendor"],
        },
      },
      {
        name: "lexicon_feed",
        description: "Competitive intelligence feed for a market or industry. Returns recent developments, entrant signals, and trend analysis.",
        inputSchema: {
          type: "object",
          properties: {
            industry: { type: "string", description: "Market or industry name" },
            limit:    { type: "number", description: "Maximum items to return (default 10)" },
          },
          required: ["industry"],
        },
      },
    ];
Behavior3/5

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

No annotations are present, so the description carries full burden. It states returns analysis with citations, implying read-only operation, but does not explicitly confirm safety, authentication needs, or other side effects.

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, front-loaded with purpose, no wasted words. Efficient and clear.

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

Completeness4/5

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

For a research tool with 3 parameters and no output schema, the description adequately explains the output format (structured PESTLE with citations) and purpose. Lacks mention of read-only nature but overall sufficient.

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 coverage is 100% with each parameter described. The description adds minimal extra meaning beyond the schema, so baseline 3 is appropriate.

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?

Description clearly states it performs 'Deep PESTLE Triangulation research on a single vendor' and returns structured analysis, distinguishing it from sibling tools like lexicon_compare_topic and lexicon_compare_vs which likely compare multiple vendors or topics.

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

Usage Guidelines3/5

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

The description implies use for single-vendor deep dives but provides no explicit guidance on when to use versus alternatives, no exclusions, and no mention of prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nadine302324-commits/lexicon-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server