Skip to main content
Glama

NovaPixel LexGrid

b2b_tech_profiler

Extracts CMS, frameworks, e-commerce tech from website, extracts VAT number from footer/legal texts, and verifies it deterministically via VIES & GLEIF.

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

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It usefully discloses that VAT verification is deterministic and performed against external registries (VIES, GLEIF), which tells the agent calls involve third-party lookups and can fail or return unverified. It does not say what happens when the VAT number is absent or invalid, whether lookups are rate-limited, or whether results include confidence values.

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?

One dense sentence that front-loads the primary extraction targets and ends with the verification method. Nothing is redundant, though the run-on comma structure makes the two distinct capabilities (tech profiling vs. VAT validation) slightly harder to scan than separate sentences would be.

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 one-parameter tool with no output schema, the description covers both output families an agent needs to know about — detected technologies and a verified VAT identity with named sources. The remaining gap is return shape and partial-failure behavior, which is a modest omission rather than a blocking one.

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?

There is a single required parameter with 100% schema description coverage, so the schema already explains that it is a target company website URL with an example. The description adds no extra semantics about the URL, such as whether it must be the root domain or whether redirects and subpages are crawled. Baseline 3 applies when the schema does the heavy lifting.

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?

States concrete verbs and resources: extracts CMS/frameworks/e-commerce tech and a VAT number from a website, then verifies it via VIES and GLEIF. The dual capability (tech stack + VAT verification) is clear, though the description doesn't distinguish this from the compliance-oriented siblings, which are also website-analysis tools.

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?

Usage is implied by the stated inputs and outputs — you call it on a company website to obtain a tech profile and validated VAT identity. There is no explicit when-to-use trigger, no prerequisite statement (e.g. the site must have a legal/footer page for VAT extraction), and no guidance about when a sibling audit tool 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources