HirePulse MCP

Private Blind Lookup

private_blind_lookup

Read-only

Hide the target from x402 facilitator metadata while running a HirePulse company or URL lookup; HirePulse and the destination still see it. Use only when facilitator privacy is required.

Instructions

Blind lookup proxy: the target is removed from x402 facilitator metadata (HirePulse and the destination still see it). Arguments are tool and target only. $0.02 single check; company_profile and due_diligence use the $0.04 bundle tier, set by the X-Private-Query-Tier header or MCP metadata hirepulse/private-tier. Use only when hiding the target from facilitator metadata is required; use the direct single-signal tools or get_company_profile otherwise. It does not hide the target from HirePulse or the destination.

Input Schema

Name	Required	Description	Default
`tool`	Yes	Lookup to execute. company_profile and due_diligence require the bundle tier selected in the HTTP header or MCP request metadata.
`target`	Yes	Bare public domain for company tools, or a public HTTP(S) URL for clean_markdown; excluded from facilitator metadata, but visible to HirePulse and the destination.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv1.0.0Oct 27, 2026

addedInput schema / properties / target / description

Added value: +"Bare public domain for company tools, or a public HTTP(S) URL for clean_markdown; excluded from facilitator metadata, but visible to HirePulse and the destination."

addedInput schema / properties / tool / description

Added value: +"Lookup to execute. company_profile and due_diligence require the bundle tier selected in the HTTP header or MCP request metadata."

addedOutput schema / anyOf

Added value: +[
+  {
+    "properties": {
+      "domain": {
+        "type": "string"
+      },
+      "privacy_guarantee": {
+        "type": "string"
+      },
+      "result": {
+        "type": "object"
+      },
+      "status": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "domain",
+      "status"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": true,
+    "properties": {
+      "code": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "status": {
+        "maximum": 599,
+        "minimum": 400,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "status",
+      "code"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / properties

Removed value: -{
-  "domain": {
-    "type": "string"
-  },
-  "privacy_guarantee": {
-    "type": "string"
-  },
-  "result": {
-    "type": "object"
-  },
-  "status": {
-    "type": "string"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "domain",
-  "status"
-]

First observedv0.1.0Oct 21, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond readOnlyHint and openWorldHint, the description discloses the privacy boundary, pricing tiers, the header/metadata mechanism for bundle pricing, and the limited argument shape. It does not contradict the annotations; it substantially enriches the behavioral context an agent needs.

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?

The purpose and privacy effect are front-loaded, followed by argument shape, pricing, usage guidance, and limitation. The paragraph is dense but has no redundant sentences; each clause contributes operational or routing information.

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?

Given annotations, full schema coverage, and an output schema, the description covers what an agent must know: what is hidden, what is not hidden, when to use it, what alternatives exist, and how tier pricing is selected. No material gap remains for correct invocation.

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 explains both tool and target, including the enum and target format. The description adds only the high-level constraint that arguments are tool and target only, plus privacy context, so it does not need to compensate for missing parameter documentation.

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 proxy operation and names the exact privacy effect: removing the target from x402 facilitator metadata. It also distinguishes this tool from direct single-signal tools and get_company_profile, so an agent can identify its role 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit condition for use ('only when hiding the target from facilitator metadata is required') and names the alternatives for the default case. It also clarifies the important boundary that HirePulse and the destination still see the target, preventing misuse based on a false privacy assumption.

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