Skip to main content
Glama
Lucacelli B2B MCP Server

Lucacelli B2B MCP Server

SaaS Competitor Pricing Tier & Feature Matrix Spy

extract_saas_competitor_pricing_matrix
Read-onlyIdempotent

Extract SaaS competitor pricing tiers, monthly and annual plan amounts, enterprise CTAs, and feature matrices from domains or pricing URLs for comparison.

Instructions

Extract SaaS competitor pricing tiers, monthly/annual plan amounts, enterprise CTAs, and feature matrices ($0.80/1k).

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": {
      "domains": "<domains>"
    },
    "name": "extract_saas_competitor_pricing_matrix"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainsYesCompetitor SaaS domains or pricing URLs, e.g. ["linear.app", "notion.so"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context by disclosing the pricing model ($0.80/1k), which matters for an open-world crawl, but it says nothing about failure behavior on non-pricing sites, rate limits, or crawling depth.

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?

A single front-loaded sentence that enumerates the extracted fields before the cost suffix. Nothing is redundant, though the parenthetical price could sit in a separate line for faster scanning.

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?

For a 1-parameter tool with no output schema, listing the extracted fields effectively substitutes for a return-value description, and the price note is a plus. However, input handling (bare domain vs pricing URL, batch limits) and crawl scope remain unspecified, leaving real gaps for an open-world scraper.

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% and the single 'domains' parameter already carries a worked example, so the schema does the heavy lifting. The description adds no constraint the schema lacks, such as a maximum number of domains or accepted URL forms, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (Extract) and a precisely bounded resource set: pricing tiers, monthly/annual plan amounts, enterprise CTAs, and feature matrices. That is far more informative than a tautology and clearly separates it from the sibling lead-scraping tools, though it never explicitly names a competing alternative such as scrape_g2_capterra_software_reviews.

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?

There is no when-to-use guidance, no prerequisites, and no exclusions. The agent is not told whether domains must be pricing-page URLs or bare domains, whether competitors can be batched, or when a different sibling (e.g. a software-review scraper) would be the better choice.

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