Skip to main content
Glama
Sign In

mcp-server

by com.interzoid
OverviewDiscussionsAdmin

interzoid_parent_company_info

Read-onlyIdempotent

Parent company and corporate ownership lookup: for any company or subsidiary, returns the parent company with its location, website, description, and a reference URL (for example Instagram to Meta Platforms). For corporate hierarchy research, account rollups, KYB, supplier risk, and sales territory planning. Cost: $0.25 USDC via x402.

Input Schema

NameRequiredDescriptionDefault
lookupYesCompany name or domain to find parent company for
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: +[
+  "Informatica"
+]
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive semantics, so the description's added value is the $0.25 USDC/x402 cost disclosure and the enumeration of returned attributes. It does not say what happens when no parent exists (standalone company) or whether results are cached, which are the remaining behavioral gaps.

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 sentences, front-loaded with the core behavior, then the canonical example, then use cases, then price. Nothing is redundant and no sentence could be removed without losing information.

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?

With no output schema, the description correctly compensates by enumerating returned fields and disclosing cost. The only missing piece for full completeness is edge-case behavior (no parent found, ambiguous matches) on a paid, open-world lookup.

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% and both parameters are fully documented in the schema, including the enum values and the default-English behavior. The description adds no parameter-level guidance beyond implying 'any company or subsidiary' is acceptable input, so 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?

The first sentence states a specific verb+resource: returns the parent company for a given company or subsidiary, along with location, website, description, and reference URL. The Instagram→Meta example makes the semantics unmistakable and clearly differentiates it in substance from siblings like interzoid_business_info or interzoid_official_name. It stops short of naming any sibling 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?

It gives concrete usage contexts (corporate hierarchy research, account rollups, KYB, supplier risk, sales territory planning), which tells an agent when the tool is appropriate. It offers no explicit exclusions or pointers to alternative tools when only basic firmographic data is needed.

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