Skip to main content
Glama

Vendors and Technology Stack

vendor-and-technology-data
Read-onlyIdempotent

Use when the user asks what technology or vendors a company uses, or wants to find companies that use a specific tool/platform.

Technology detection via SSL certificates, JavaScript analysis, and meta tag inspection — including whitelabeled products and integrations.

Bidirectional lookup:

  • As a client: Find what vendors/technologies a company uses (e.g., "what does notion.so use?")

  • As a vendor: Find companies using this domain as a vendor (e.g., "who uses stripe.com?")

Paginated: returns up to max_records (default 100, max 10000); use offset to page through total. Vendor-mode lookups against popular SaaS (e.g. shopify.com, google.com) commonly have tens of thousands of clients — start with a small max_records.

Available fields for the 'fields' parameter: client_domain, client_fqdn, vendor_domain, vendor_fqdn, record_date. Field details: https://docs.discolike.com.

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": {
      "filters": "<filters>"
    },
    "name": "vendor-and-technology-data"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOutput fields to include in response
formatNoResponse format: 'rows' or 'columnar'rows
offsetNoNumber of records to skip for pagination. Default 0.
contextNoWhy you are calling this tool, in a few words. No names or emails.
filtersYesRequest model for the /vendors endpoint.
llm_modelNoYour model id, or "unknown".
max_recordsNoMaximum records to return (1-10000). Default 100. Use offset to paginate.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Output Schema

NameRequiredDescriptionDefault
countNo
totalNo
offsetNo
vendorsNo
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / properties
      Added value: +{
      +  "_mcp_instructions": {
      +    "description": "Server-issued metadata for this conversation.",
      +    "properties": {
      +      "conversation_id": {
      +        "description": "The server-issued conversation identifier.",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "count": {
      +    "type": "integer"
      +  },
      +  "offset": {
      +    "type": "integer"
      +  },
      +  "total": {
      +    "type": "integer"
      +  },
      +  "vendors": {
      +    "anyOf": [
      +      {
      +        "items": {
      +          "properties": {
      +            "client_domain": {
      +              "type": "string"
      +            },
      +            "client_fqdn": {
      +              "type": "string"
      +            },
      +            "record_date": {
      +              "type": "string"
      +            },
      +            "vendor_domain": {
      +              "type": "string"
      +            },
      +            "vendor_fqdn": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      {
      +        "additionalProperties": {
      +          "items": {},
      +          "type": "array"
      +        },
      +        "required": [],
      +        "type": "object"
      +      }
      +    ]
      +  }
      +}
    • addedOutput schema / required
      Added value: +[]
  2. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Why you are calling this tool, in a few words. No names or emails.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Your model id, or \"unknown\".",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely non-structured context: the detection methodology, that whitelabeled products and integrations are included, and a data-volume warning for vendor-mode lookups. It stops short of describing failure behavior for unknown domains or how stale the certificate-derived data may be.

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 with the 'Use when' trigger, then a short methodology line, a bulleted two-mode breakdown, and a pagination note — a sensible ordering for an agent scanning for relevance. Minor waste in restating max_records' default and maximum values that the schema already carries, though the accompanying volume warning justifies keeping that sentence.

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 an 8-parameter tool with nested filters and an output schema, the description covers the parts an agent must reason about: which mode to pick, which fields to request, and how to page safely. It leaves the 'format' rows-vs-columnar choice and non-answer behavior for missing domains unexplained, but those are peripheral given the schema and output schema already document them.

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%, so the baseline is 3. The description does add real meaning beyond the schema in two places — it enumerates the concrete values accepted by 'fields' (client_domain, client_fqdn, vendor_domain, vendor_fqdn, record_date) where the schema only says 'Output fields to include', and it explains the client/vendor match semantics. The pagination advice largely restates max_records and offset defaults already in the schema.

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 names a specific resource (vendor/technology data for a domain) and a specific capability (technology detection via SSL certificates, JavaScript analysis, and meta tag inspection). The bidirectional framing — client mode ('what does notion.so use?') vs vendor mode ('who uses stripe.com?') — makes the tool's scope unambiguous and impossible to confuse with the CRM or contact-oriented siblings.

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

Usage Guidelines4/5

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

It opens with an explicit trigger: 'Use when the user asks what technology or vendors a company uses, or wants to find companies that use a specific tool/platform.' It also gives a practical operating guideline — start with a small max_records in vendor mode because popular SaaS domains have tens of thousands of clients. It does not name a when-not condition or an alternative tool, which keeps it short of a 5.

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