Skip to main content
Glama

HSH Data-on-Demand

by io.github.hshintelligence
OverviewDiscussionsAdmin

hsh-b2b-contact

Named decision-makers at companies, with the role each actually holds. Two sources: officers and directors named in US securities filings, with the title as filed, and accelerator-cohort founders with an email address where one survives validation. Every call returns a real sample built at that moment, plus a count of how many records carry the named person's own address, how many carry a shared company inbox, and how many carry none — so a batch is judged before it is bought. Priced on request. No personal telephone numbers (a company number only where its own site publishes one), no per-person profile links and no bounce-rate guarantee; see not_offered on any response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
liveNoRead each company's own site during the call (default true). Adds the company's current inbox, phone and links, each with provenance.
roleNoMatches the job title as stated on the filing (e.g. 'Chief Executive', 'Chief Financial').
sourceNo'both' (default), 'filings' for named officers with filed titles, or 'cohort' for founders with validated addresses.
tickerNoRestrict to one listed company.
dry_runNoReturn the sample and the quote without opening an order.
industryNoMatches the filed industry description, or the cohort's industry label.
locationNoCity, state or country. Cohort records only — filings do not carry a person's location.
quantityYesRecords wanted (1-100000). A real sample is returned now; the batch is quoted.
live_budgetNoHard ceiling on how many records get a live pass (default and maximum 25). Roughly five page fetches and two seconds each.
buyer_contactNoHow to reach you about the quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / live
      Added value: +{
+  "description": "Read each company's own site during the call (default true). Adds the company's current inbox, phone and links, each with provenance.",
+  "type": "string"
+}
    • addedInput schema / properties / live_budget
      Added value: +{
+  "description": "Hard ceiling on how many records get a live pass (default and maximum 25). Roughly five page fetches and two seconds each.",
+  "type": "number"
+}
  2. Changed8 schema fields changed
    • addedInput schema / properties / buyer_contact
      Added value: +{
+  "description": "How to reach you about the quote.",
+  "type": "string"
+}
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "Return the sample and the quote without opening an order.",
+  "type": "string"
+}
    • changedInput schema / properties / industry / description
      Previous value: -"Industry filter (e.g., 'D2C skincare', 'B2B SaaS')."New value: +"Matches the filed industry description, or the cohort's industry label."
    • changedInput schema / properties / location / description
      Previous value: -"City, state, or country."New value: +"City, state or country. Cohort records only — filings do not carry a person's location."
    • changedInput schema / properties / quantity / description
      Previous value: -"Number of contacts needed (1-100000)."New value: +"Records wanted (1-100000). A real sample is returned now; the batch is quoted."
    • changedInput schema / properties / role / description
      Previous value: -"Job title or role (e.g., 'CTO', 'Founder', 'Head of Marketing')."New value: +"Matches the job title as stated on the filing (e.g. 'Chief Executive', 'Chief Financial')."
    • addedInput schema / properties / source
      Added value: +{
+  "description": "'both' (default), 'filings' for named officers with filed titles, or 'cohort' for founders with validated addresses.",
+  "type": "string"
+}
    • addedInput schema / properties / ticker
      Added value: +{
+  "description": "Restrict to one listed company.",
+  "type": "string"
+}
  3. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose important behaviors: a real sample is built per call, counts of address types are returned, and certain fields are never offered. It does not mention that a call may open an order unless dry_run is set, nor that live=true reads company websites during the call, though these are partially implied by the schema.

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 is a dense paragraph but each sentence adds value, covering product definition, sample mechanics, pricing, and exclusions. It is longer than ideal but not wasteful, and the most important information is front-loaded.

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 the tool's complexity, no annotations, and no output schema, the description covers the key operational aspects: sample generation, quality counts, pricing model, and explicit non-offerings. It does not fully explain the order flow or how buyer_contact and dry_run interact, but the schema covers those parameters.

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 all parameters. The description adds useful context about sources and validation but does not add per-parameter meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 clearly identifies the resource: named decision-makers at companies with the roles they actually hold, sourced from securities filings and accelerator cohorts. It is specific about what is delivered, though it does not explicitly contrast itself with sibling tools like hsh-b2b-enriched or hsh-b2b-full.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies usage by describing the data product, sample behavior, and exclusions such as no personal phone numbers and no bounce-rate guarantee. However, it does not explicitly state when to prefer this tool over the sibling B2B tools or provide alternative routing.

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

All HSH Data-on-Demand 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