Orivale Agent Intelligence

orivale_b2b_domain_enrich

Read-onlyIdempotent

Enrich a B2B company domain with hiring/API buying signals, ICP fit score (0-100), and 2-line cold-outreach icebreaker (use orivale_tech_stack_signal for 30+ framework/pixel detection).

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": "orivale_b2b_domain_enrich"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Bare company domain without scheme (e.g. stripe.com)
`x402_payment`	No	Optional Base64 x402 PAYMENT-SIGNATURE (Base/Solana USDC) to unlock full payload.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 13, 2026

changedInput schema / properties / domain / description

Previous value: -"Company domain (e.g. stripe.com)"New value: +"Bare company domain without scheme (e.g. stripe.com)"

addedInput schema / properties / domain / maxLength
```
Added value: +253
```
addedInput schema / properties / domain / minLength
```
Added value: +4
```

addedInput schema / properties / domain / pattern

Added value: +"^[a-zA-Z0-9](?:[a-zA-Z0-9-]{0,61}[a-zA-Z0-9])?(?:\\.[a-zA-Z]{2,})+$"

changedInput schema / properties / x402_payment / description

Previous value: -"Optional Base64 x402 PAYMENT-SIGNATURE"New value: +"Optional Base64 x402 PAYMENT-SIGNATURE (Base/Solana USDC) to unlock full payload."

addedInput schema / properties / x402_payment / maxLength
```
Added value: +8192
```
addedInput schema / properties / x402_payment / minLength
```
Added value: +16
```

First observedNov 13, 2026

TDQS

A4.2/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. The description adds what the agent does not otherwise know: the payload contains scoring and generated outreach copy, including the 0-100 ICP scale, which matters for interpreting results. It omits that only a partial payload is returned unless the x402 payment is supplied, though the schema does document that parameter.

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?

A single sentence front-loads the core action and its outputs, with the sibling routing compactly parenthesized at the end. There is no filler and every clause carries 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 carries the burden of describing returns and does so by naming the three payload components and the ICP scale. It is nearly complete for a two-parameter enrichment tool, but does not characterize response shape or what partial results look like without payment.

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%, with the domain pattern and the x402_payment unlock parameter both documented inline. The description reinforces that the target is a company domain rather than a URL, but adds no format, normalization, or payment semantics beyond what the schema states, so the baseline 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?

Uses a specific verb (enrich) on a specific resource (B2B company domain) and enumerates the concrete outputs: hiring/API buying signals, ICP fit score on a 0-100 scale, and a 2-line icebreaker. It also explicitly distinguishes itself from the sibling orivale_tech_stack_signal, so an agent can tell the two apart without opening either schema.

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?

Gives an explicit routing rule: use orivale_tech_stack_signal instead when the goal is 30+ framework/pixel detection. That is a clear alternative-selection condition, but there is no broader when-to-use or when-not-to-use framing (e.g. filtering-only lookups) and no mention of prerequisites such as the payment signature needed for the full payload.

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

All Orivale Agent Intelligence tools Inspect

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.