Identify the complete technology stack used by a company or website from a domain lookup, including CMS, frontend frameworks, backend technologies, web server, hosting provider, CDN, analytics, security technologies, and e-commerce platform. Premium API. Cost: $0.25 USDC via x402.
| Name | Required | Description | Default |
|---|---|---|---|
| lookup | Yes | Domain name or company website to identify the tech stack for |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description claims a non-destructive lookup, but annotations set destructiveHint: true, a direct contradiction. Additionally, while cost is mentioned, no side effects or permission requirements are disclosed, so behavioral transparency is poor.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that immediately states the tool's purpose and key output, plus cost info. No extraneous text; front-loaded and to the point.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Although the description lists technology categories, it does not explain the output format or structure, and there is no output schema. For a tool with moderate complexity and no output schema, the description should provide more detail on return values, leaving it incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with the parameter well-described in the schema. The description adds the same information ('domain name or company website') but no additional format, examples, or constraints, so baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool identifies the complete technology stack from a domain lookup, listing numerous technology categories. This verb+resource combination is specific and distinct from sibling tools which cover addresses, companies, and other data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for tech stack analysis, and sibling tools are clearly different in purpose, so usage context is clear. However, it lacks explicit guidance on when to use this versus alternatives or any when-not conditions, which prevents a higher score.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target distinct data operations (matching, standardization, enrichment) with clear descriptions. Minor overlaps exist, e.g., address_match_advanced vs global_address_match, but descriptions differentiate them.
All tools follow a consistent 'interzoid_descriptive_function' pattern in snake_case, making it easy to predict purpose from the name.
58 tools is high for a single server, exceeding the typical 3-15 range. While each serves a specific data enrichment function, the quantity may overwhelm agents without clear categorization.
The tool surface covers a broad domain including address, company, person, and financial data. Minor gaps exist (e.g., no reverse IP lookup, limited social media coverage), but core data needs are well-addressed.
