Orivale Agent Intelligence

orivale_tech_stack_signal

Read-onlyIdempotent

Fingerprint 30+ B2B website technologies across Frontend, CDN, Pixels, CRM, Payments, Auth & Security Headers (use orivale_b2b_domain_enrich for ICP outreach copy).

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_tech_stack_signal"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Target company domain without scheme (e.g. linear.app)
`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: -"Target company domain (e.g. linear.app)"New value: +"Target company domain without scheme (e.g. linear.app)"

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

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds the category breadth but omits the most consequential behavior: only a partial payload is returned unless an x402 payment signature is supplied, which is buried in the schema rather than surfaced here. For an open-world tool with a paid unlock tier, that gap keeps it at a 3.

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 with zero filler; the capability and the sibling redirect are both front-loaded within it. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should sketch what a fingerprint result looks like and how the paid unlock differs from the default response; it does neither. The annotations and rich schema carry the rest, making it adequate but with a clear disclosure gap.

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 a concrete example ('linear.app') already documented in the schema, so baseline is 3. The description adds no meaning beyond the parameters and never hints that x402_payment changes the payload depth.

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?

Names a specific verb ('Fingerprint'), the resource ('B2B website technologies'), the scale ('30+'), and the exact categories covered. The parenthetical explicitly routes a different need to orivale_b2b_domain_enrich, so an agent can separate this from its sibling without opening the 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?

The parenthetical establishes an explicit alternative for ICP outreach copy, which is real when-to-use-what guidance. It stops short of stating prerequisites or when-not to fingerprint at all, so it doesn't reach the fully-explicit tier.

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.