Skip to main content
Glama

YRUZ Company Enrich (0.01 USDC)

company_enrich
Read-onlyIdempotent

Company enrichment from a domain or email in one call: company name, description, logo, favicon, social profiles (LinkedIn, X, GitHub, Facebook, Instagram, YouTube ...), contact emails and phones published on the site, email provider (Google Workspace, Microsoft 365 ...), tech stack (CMS, framework, hosting, CDN, analytics, payments), schema.org organization data and domain registration age. For lead qualification, KYB and CRM enrichment. Price: 0.01 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"company_enrich"}. Same tool over HTTP: https://yruz.one/api/enrich?domain=stripe.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": {
      "domain": "<domain>"
    },
    "name": "company_enrich"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYescompany domain (required), e.g. stripe.com; a URL or email works too

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / domain / examples
      Added value: +[
      +  "stripe.com"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, but the description adds important commercial and failure behavior: 0.01 USDC per call via x402, invalid input refused before payment, failed runs never charged, and PaymentRequired without payment. This is substantive context beyond the annotations without contradicting them.

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?

The description is front-loaded with the resource and return fields, then layers in use cases, payment mechanics, and invocation guidance. It is dense and includes some optional invocation details such as the HTTP URL, but the payment and failure semantics earn their place for a paid x402 tool.

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?

With no output schema, the description carries the burden of explaining return values, and it does so thoroughly by enumerating company fields, social profiles, contact data, email provider, tech stack, schema.org data, and domain age. It also explains payment and failure behavior, making the definition complete enough for an agent to invoke it 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%, and the schema already documents the domain parameter with examples and notes that a URL or email works. The description repeats 'from a domain or email' but adds no parameter syntax or format details beyond what the schema provides, so the baseline of 3 applies.

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 states a specific resource and action: company enrichment from a domain or email in one call. It enumerates the returned data fields in detail, making it clear this is not a generic domain lookup and helping distinguish it from siblings such as domain_intel or site_audit.

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 provides clear usage contexts: 'For lead qualification, KYB and CRM enrichment.' It also points to get_example for invocation, but it does not explicitly say when to prefer sibling tools like domain_intel or web_extract instead.

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.