Skip to main content
Glama

Company tool stack

company_stack
Read-only

Find which tools a company uses (client portals, practice software, email, CRM, analytics), from its website and DNS. Every tool comes with the evidence that was observed and a confidence. Absence of a tool means no evidence was found, not that the company does not use it.

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": {
      "domain": "<domain>"
    },
    "name": "company_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe company website, e.g. example-cpa.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered by structured data. The description adds real behavioral context beyond that: each result carries the observed evidence and a confidence score, and negative results are explicitly framed as absence-of-evidence. It does not cover latency, coverage limits, or how confidence is computed, keeping it short of a 5.

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?

Three tight sentences with zero filler, front-loading what is detected before the caveat about negative results. Every sentence carries information an agent needs.

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?

No output schema exists, yet the description explains the return shape (tool plus evidence plus confidence), which is the key thing an agent needs to consume results. For a single-parameter read-only lookup this is nearly complete; only detection coverage or reliability limits remain unstated.

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 there is only one parameter, so the schema already defines the domain input including an example. The description only reinforces that the domain is the company's website and that DNS-derived signals are also used, which is marginal extra meaning. Baseline 3 is appropriate.

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 and resource ("Find which tools a company uses") plus the concrete categories detected and the detection sources (website and DNS). This is clearly distinguishable from the logo-related siblings, which cover none of the same ground.

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?

Conveys the use case implicitly (discovering a company's software stack) and adds a valuable interpretation rule: absence of a tool means no evidence, not non-usage. However, it never states when to prefer this tool over other research approaches, nor any prerequisites such as whether the domain must be the primary/canonical website.

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