Skip to main content
Glama
edtool79-collab

HirePulse MCP

by edtool79-collab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Pre-Purchase Merchant Check

pre_purchase_merchant_trust_check
Read-only

Check an unfamiliar online shop before buying: get structured public trust evidence, a cautious evidence score, risk flags, missing signals, and explicit limits. It cannot certify safety.

Instructions

Returns structured public evidence and explicit unknowns. Public trust evidence for an unfamiliar online shop before buying: a cautious evidence score, risk flags, missing signals and limits. Cannot certify safety. $0.005 after the shared free calls. x402 API endpoints: x402_merchant_trust_check. Use for a consumer purchase from an unfamiliar shop; use b2b_vendor_stability_evaluator for B2B supplier procurement. This does not buy goods or authorize payment.

Input Schema

NameRequiredDescriptionDefault
domainYesPublic domain without scheme, path or port.
contextNoOptional. A few words on why you are calling this tool. Recorded without your identity to improve the tools; leave out personal data.
merchant_wallet_or_idNoOptional merchant identifier as context; supplying a wallet does not establish ownership or on-chain reputation.
transaction_amount_usdNoOptional intended purchase value in USD as context; it does not authorize a purchase or change the scan price.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 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"
+}
    • changedInput schema / properties / domain / examples
      Previous value: -[
-  "example.com"
-]New value: +[
+  "allbirds.com"
+]
    • addedInput schema / properties / merchant_wallet_or_id / description
      Added value: +"Optional merchant identifier as context; supplying a wallet does not establish ownership or on-chain reputation."
    • addedInput schema / properties / transaction_amount_usd / description
      Added value: +"Optional intended purchase value in USD as context; it does not authorize a purchase or change the scan price."
    • addedOutput schema / anyOf
      Added value: +[
+  {
+    "description": "Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null.",
+    "properties": {
+      "domain": {
+        "type": "string"
+      },
+      "error_reason": {
+        "type": "string"
+      },
+      "latency_ms": {
+        "minimum": 0,
+        "type": "integer"
+      },
+      "limitations": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "recommendation": {
+        "type": "string"
+      },
+      "risk_level": {
+        "enum": [
+          "LOW",
+          "MEDIUM",
+          "HIGH",
+          "CRITICAL"
+        ],
+        "type": "string"
+      },
+      "safe_to_buy": {
+        "type": "boolean"
+      },
+      "signals": {
+        "properties": {
+          "active_ad_campaigns": {
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "domain_age_days": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "has_active_employees": {
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "legitimate_tech_stack": {
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "onchain_reputation_score": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "open_jobs_count": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "domain_age_days",
+          "has_active_employees",
+          "open_jobs_count",
+          "legitimate_tech_stack",
+          "active_ad_campaigns",
+          "onchain_reputation_score"
+        ],
+        "type": "object"
+      },
+      "status": {
+        "enum": [
+          "ok",
+          "no_data",
+          "unreachable"
+        ],
+        "type": "string"
+      },
+      "trust_score": {
+        "maximum": 100,
+        "minimum": 0,
+        "type": "number"
+      }
+    },
+    "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 / description
      Removed value: -"Only status=ok is charged. Diagnostic results may omit result fields; unknown facts are null."
    • removedOutput schema / properties
      Removed value: -{
-  "domain": {
-    "type": "string"
-  },
-  "error_reason": {
-    "type": "string"
-  },
-  "latency_ms": {
-    "minimum": 0,
-    "type": "integer"
-  },
-  "limitations": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "recommendation": {
-    "type": "string"
-  },
-  "risk_level": {
-    "enum": [
-      "LOW",
-      "MEDIUM",
-      "HIGH",
-      "CRITICAL"
-    ],
-    "type": "string"
-  },
-  "safe_to_buy": {
-    "type": "boolean"
-  },
-  "signals": {
-    "properties": {
-      "active_ad_campaigns": {
-        "type": [
-          "boolean",
-          "null"
-        ]
-      },
-      "domain_age_days": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "has_active_employees": {
-        "type": [
-          "boolean",
-          "null"
-        ]
-      },
-      "legitimate_tech_stack": {
-        "type": [
-          "boolean",
-          "null"
-        ]
-      },
-      "onchain_reputation_score": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "open_jobs_count": {
-        "type": [
-          "number",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "domain_age_days",
-      "has_active_employees",
-      "open_jobs_count",
-      "legitimate_tech_stack",
-      "active_ad_campaigns",
-      "onchain_reputation_score"
-    ],
-    "type": "object"
-  },
-  "status": {
-    "enum": [
-      "ok",
-      "no_data",
-      "unreachable"
-    ],
-    "type": "string"
-  },
-  "trust_score": {
-    "maximum": 100,
-    "minimum": 0,
-    "type": "number"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "domain",
-  "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?

With readOnlyHint=true and openWorldHint=true already declared, the description adds important behavioral context: it returns explicit unknowns, cannot certify safety, costs $0.005 after shared free calls, and does not buy goods or authorize payment. These details clarify the tool's limits and cost without contradicting the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description front-loads the core return value and then covers limits, pricing, endpoint alias, and usage guidance. It is mostly efficient, though there is some redundancy between 'structured public evidence' and 'Public trust evidence' and the endpoint mention could be clearer.

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 the existing output schema, read-only annotations, and fully documented parameters, the description supplies the remaining decision-critical context: purpose, scope, cost, safety limits, and B2B alternative. An agent has enough information to decide when and how to invoke it.

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%, so the schema already documents the domain, context, merchant identifier, and transaction amount parameters in detail. The description provides only general framing around public trust evidence for an online shop and does not add parameter-specific semantics beyond the schema.

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 resource and outcome: public trust evidence, a cautious evidence score, risk flags, missing signals and limits for an unfamiliar online shop before buying. It distinguishes the consumer-purchase use case from B2B supplier procurement by naming the b2b_vendor_stability_evaluator sibling.

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 explicitly says to use this tool for a consumer purchase from an unfamiliar shop and names b2b_vendor_stability_evaluator for B2B supplier procurement. It also clarifies that the tool does not buy goods or authorize payment, though it does not explain when to choose this over the x402_merchant_trust_check sibling.

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