Skip to main content
Glama

b2b_tech_profiler

Read-onlyIdempotent

[Web scraping & KYB verification. Read-only, non-destructive, side-effect free]. Analyzes website tech stacks (CMS, frameworks, e-commerce engines), extracts VAT numbers and legal entities from footers and privacy policies, and verifies them deterministically via VIES & GLEIF. Usage: Use this tool when starting with a company website URL to discover its tech stack and corporate identity. If you already have an EU VAT number and need direct registry lookup, use 'vies_gleif_kyb_verify' instead. Returns: JSON object with { url: string, technologies: { cms: string | null, ecommerce: string | null, analytics: string[], frameworks: string[] }, extractedVat: string | null, kybVerification: object | null }.

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": {
      "url": "<url>"
    },
    "name": "b2b_tech_profiler"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesTarget company website URL (e.g. https://novapixel.it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnlyHint and idempotentHint, and the bracketed line restates them, which earns no extra credit. Beyond that, the description discloses the extraction sources (footers, privacy policies) and that verification is deterministic against external registries — useful context about how results are produced. It stops short of latency, rate limits, or behavior when no VAT is found.

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?

Front-loaded purpose, then labelled Usage and Returns sections — easy to scan. Slightly padded by the bracketed safety restatement that duplicates the annotations, and by restating return shape that could be terser.

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

Completeness5/5

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

With no output schema and only one parameter, the description still supplies the full return shape (technologies breakdown, extractedVat, kybVerification), so an agent can plan downstream handling without a schema. Nothing material is missing for a single-URL tool.

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 a single required 'url' that already carries an example. The description adds only the framing that this is a company website URL rather than a registry identifier, so the baseline of 3 applies.

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?

States a specific verb set (analyzes, extracts, verifies) over named resources (website tech stack, VAT numbers, legal entities) and names the concrete verification backends (VIES, GLEIF). An agent knows immediately this is a URL-seeded profiler plus KYB check.

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

Usage Guidelines5/5

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

Explicitly states the entry condition ('when starting with a company website URL') and the exclusion with a named alternative: if you already hold an EU VAT number, use 'vies_gleif_kyb_verify'. That is a genuine when/when-not routing rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources