Skip to main content
Glama
Sign In

mcp-server

by com.interzoid
OverviewDiscussionsAdmin

interzoid_business_info

Read-onlyIdempotent

Company data enrichment (firmographics): look up any company by name, web domain, or email address and get its official name, website, headquarters address, description, revenue, employee count, NAICS code, and top executive with title. For lead enrichment, CRM enrichment, account research, and KYB checks, for public and private companies. Cost: $0.25 USDC via x402.

Input Schema

NameRequiredDescriptionDefault
lookupYesCompany name, website, or email
languageNoOptional. Two-letter code for results in that language (default English): fr, de, it, es, ja, pt, zh, ar, nl, el, tr, ko, sv, vi, th, id. Same price in every language.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
+  "description": "Optional. Two-letter code for results in that language (default English): fr, de, it, es, ja, pt, zh, ar, nl, el, tr, ko, sv, vi, th, id. Same price in every language.",
+  "enum": [
+    "fr",
+    "de",
+    "it",
+    "es",
+    "ja",
+    "pt",
+    "zh",
+    "ar",
+    "nl",
+    "el",
+    "tr",
+    "ko",
+    "sv",
+    "vi",
+    "th",
+    "id"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / lookup / examples
      Added value: +[
+  "Cisco"
+]
  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 declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered structurally. The description adds genuinely new behavioral context: the call costs $0.25 USDC via x402 and works for both public and private companies. It omits any mention of failure/not-found behavior or latency.

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: capability and returned fields first, then use cases, then cost. Every sentence carries information an agent needs and nothing is repeated.

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?

There is no output schema, so the description's enumeration of returned fields (official name, website, HQ address, description, revenue, employee count, NAICS, top executive) is essential and present. Combined with cost and scope, an agent has enough to decide and call correctly.

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%, so both parameters are already documented, and the description's phrase 'by name, web domain, or email address' largely restates the schema's 'Company name, website, or email'. The optional language parameter and its price neutrality are not mentioned in the description, but the schema covers them. Baseline 3 applies.

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 a specific verb (look up) and resource (any company) plus the three accepted identifier types (name, web domain, email) and enumerates the returned firmographic fields. That makes it clearly distinguishable from siblings like interzoid_official_name or interzoid_company_verification, though no sibling is named explicitly.

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?

Names concrete contexts: lead enrichment, CRM enrichment, account research, and KYB checks, and states the coverage scope as public and private companies. It does not say when to prefer a sibling such as interzoid_business_info_name or interzoid_parent_company_info instead, so there are no exclusions.

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

All mcp-server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources