Lexicon Intelligence

lexicon_compare_vs

Compare two vendors or products head-to-head using live evidence from 20 independent sources and PESTLE Triangulation to generate a structured comparison report.

Instructions

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.

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": {
      "vendorA": "<vendorA>",
      "vendorB": "<vendorB>"
    },
    "name": "lexicon_compare_vs"
  }
}

Input Schema

Name	Required	Description
`vendorA`	Yes	First vendor or product name
`vendorB`	Yes	Second vendor or product name
`industry`	No	Industry context (e.g. fintech, healthcare, SaaS)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 5, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description reveals that the tool retrieves live evidence from 20 sources and applies PESTLE Triangulation, providing some transparency. However, without annotations, it lacks details on potential side effects, required permissions, or output format.

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?

The description is extremely concise, consisting of two sentences that effectively front-load the purpose and key behavioral aspects. No superfluous words.

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?

Given the absence of an output schema and the presence of sibling tools, the description is somewhat sparse. It explains the basic behavior but could better prepare the agent for interpreting results or handling errors.

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 has 100% description coverage, so the baseline is 3. The description reinforces the schema by referring to 'vendors or products' and 'industry context', but adds no extra semantic nuance beyond what is already in the parameter 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 the tool's core function: comparing two vendors or products head-to-head. It mentions retrieving live evidence and applying PESTLE Triangulation, making the purpose distinct from sibling tools like lexicon_compare_methodology or lexicon_compare_topic.

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 text implies when to use the tool (for comparing two vendors/products) but does not explicitly state when not to use it or suggest alternatives. No guidance on prerequisites or context limits is provided.

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

Deploy Server