Skip to main content
Glama

HirePulse Company Research

by xyz.gethirepulse.api
OverviewDiscussionsAdmin

Claim a free 25-call trial

claim_free_trial

One-time pass: 25 successful calls shared across supported single-domain tools, valid 30 days and independent of IP. Excludes private lookup, quote redemption and paid email inboxes. Send one active Base wallet or work email (no email sent). Use X-Trial-Token or MCP metadata hirepulse/trial_token.

Input Schema

NameRequiredDescriptionDefault
emailNoA work email address; free mailbox providers are not accepted.
walletNoA Base address with at least one transaction or $0.10 USDC.

Output Schema

NameRequiredDescriptionDefault
callsYes
statusYes
expires_atYes
how_to_useYes
trial_tokenYesSecret bearer capability. Keep private; never publish or log.
demo_domains_always_freeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / oneOf
      Added value: +[
+  {
+    "not": {
+      "required": [
+        "email"
+      ]
+    },
+    "required": [
+      "wallet"
+    ]
+  },
+  {
+    "not": {
+      "required": [
+        "wallet"
+      ]
+    },
+    "required": [
+      "email"
+    ]
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "calls": {
+      "const": 25,
+      "type": "integer"
+    },
+    "demo_domains_always_free": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "expires_at": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "how_to_use": {
+      "properties": {
+        "http_header": {
+          "type": "string"
+        },
+        "mcp": {
+          "type": "string"
+        },
+        "note": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "status": {
+      "const": "ok",
+      "type": "string"
+    },
+    "trial_token": {
+      "description": "Secret bearer capability. Keep private; never publish or log.",
+      "pattern": "^hpt_[a-f0-9]{48}$",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "trial_token",
+    "calls",
+    "expires_at",
+    "how_to_use",
+    "demo_domains_always_free"
+  ],
+  "type": "object"
+}
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond annotations: 25 successful calls, shared quota, 30-day validity, IP independence, exclusions, no email sent, and token delivery via X-Trial-Token or MCP metadata. This is consistent with readOnlyHint=false and openWorldHint=true.

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 description is dense and front-loaded: quota, validity, exclusions, acceptable inputs, and token mechanism are all stated without filler. Every sentence carries operational 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?

With an output schema present, the description need not explain return values. It covers the key call semantics, eligibility, exclusions, and token usage, making it complete for this tool.

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 the schema already documents the wallet and email parameters and their constraints. The description reinforces the one-of choice and notes that no email is sent, but adds little parameter syntax beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope: a one-time 25-call trial valid for 30 days, shared across supported single-domain tools. It names exclusions (private lookup, quote redemption, paid email inboxes), which helps differentiate it from some siblings, though it does not explicitly map to all sibling tools.

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 clearly explains when the trial applies and what is excluded, plus the one-time and 30-day constraints. It stops short of naming alternative tools for excluded use cases, but the usage context is otherwise clear.

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

All HirePulse Company Research toolsInspect
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.

Resources