Skip to main content
Glama
edtool79-collab

HirePulse MCP

by edtool79-collab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Find Hot Buyers

find_hot_buyers
Read-only

Scan 2-25 company domains to discover which are hiring hardest based on intent scores; pay only for detailed profiles of hot companies.

Instructions

Finds which of 2 to 25 company domains are hiring hardest. Step 1 is a free scan that returns each intent_score and a quote_id; step 2 pays $0.25 per hot company (at most 4, $1.00) for a full profile of each. No hot company means no charge. 3 free scans per day.

Input Schema

NameRequiredDescriptionDefault
contextNoOptional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.
domainsNoPublic company domains without a URL scheme, path or port.
quote_idNoquote_id from step 1. Send it alone to pay and receive the results.
min_intent_scoreNoMinimum hiring intent score (0–100) for a company to be included in the paid hot-company quote.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.0.0
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Optional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.",
+  "type": "string"
+}
    • addedInput schema / properties / min_intent_score / description
      Added value: +"Minimum hiring intent score (0–100) for a company to be included in the paid hot-company quote."
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "properties": {
+      "billable_count": {
+        "type": "integer"
+      },
+      "cold": {
+        "description": "hot-buyers: domains below the threshold, free.",
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "expires_at": {
+        "format": "date-time",
+        "type": "string"
+      },
+      "next": {
+        "type": "string"
+      },
+      "price_micro_usd": {
+        "type": "integer"
+      },
+      "price_usd": {
+        "type": "number"
+      },
+      "quote_id": {
+        "type": "string"
+      },
+      "results": {
+        "description": "Paid rows, after step 2.",
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "status": {
+        "description": "quote: pay with quote_id to get the results. nothing_billable: no charge. ok: paid results.",
+        "enum": [
+          "quote",
+          "nothing_billable",
+          "ok"
+        ],
+        "type": "string"
+      },
+      "statuses": {
+        "description": "Status of every domain, free.",
+        "items": {
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "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: -{
-  "billable_count": {
-    "type": "integer"
-  },
-  "cold": {
-    "description": "hot-buyers: domains below the threshold, free.",
-    "items": {
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "expires_at": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "next": {
-    "type": "string"
-  },
-  "price_micro_usd": {
-    "type": "integer"
-  },
-  "price_usd": {
-    "type": "number"
-  },
-  "quote_id": {
-    "type": "string"
-  },
-  "results": {
-    "description": "Paid rows, after step 2.",
-    "items": {
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "status": {
-    "description": "quote: pay with quote_id to get the results. nothing_billable: no charge. ok: paid results.",
-    "enum": [
-      "quote",
-      "nothing_billable",
-      "ok"
-    ],
-    "type": "string"
-  },
-  "statuses": {
-    "description": "Status of every domain, free.",
-    "items": {
-      "type": "object"
-    },
-    "type": "array"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "status"
-]
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations by disclosing cost ($0.25 per hot company, capped at $1.00), the no-hot-company no-charge guarantee, and the 3-free-scans-per-day quota — all behavior an agent cannot infer from readOnlyHint/openWorldHint. The only mild tension is that a paid charge is an external side effect even though the tool is flagged read-only for data; that is a scoping convention rather than a direct contradiction.

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?

Four short sentences, front-loaded with what the tool does, then sequencing, then cost, then quota. Nothing is redundant with the title and every sentence carries operative 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?

Given an output schema, return values need not be explained, and the description still previews intent_score and quote_id. It covers cost, quota, and the step gating completely; only the relationship to neighboring hiring-intent tools is left implicit.

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%, so domains, quote_id, min_intent_score, and context are already documented in the schema. The description reinforces the quote_id handoff role and the 2–25 domain range, but adds no format or threshold detail 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?

Names a specific verb and resource ('Finds which of 2 to 25 company domains are hiring hardest') and immediately frames the two-step scan/quote design. This is distinguishable at a glance from siblings like get_company_hiring_intent, which scores a single company rather than ranking a batch.

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 two-step protocol is spelled out concretely: step 1 free scan returns intent_score and quote_id, step 2 redeems the quote_id to pay. It does not, however, tell the agent when to prefer this over get_company_hiring_intent or when a single-company lookup is more appropriate.

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

Deploy Server

Other Tools