Skip to main content
Glama

HSH Data-on-Demand

by io.github.hshintelligence
OverviewDiscussionsAdmin

hsh-b2b-enriched

Everything in the named-contacts product, plus the company around the person: industry, location, headcount, stage, ticker, exchange, state of incorporation and entity type, from the same two sources and the filed entity record. A real sample on every call, priced on request. No LinkedIn URL — no source here holds a per-person profile link.

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. Changed12 schema fields changed
    • addedInput schema / properties / buyer_contact
      Added value: +{
+  "description": "How to reach you about the quote.",
+  "type": "string"
+}
    • removedInput schema / properties / company_size
      Removed value: -{
-  "description": "Range like '11-50' or '500+'.",
-  "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: -""New value: +"Matches the filed industry description, or the cohort's industry label."
    • 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"
+}
    • addedInput schema / properties / location
      Added value: +{
+  "description": "City, state or country. Cohort records only — filings do not carry a person's location.",
+  "type": "string"
+}
    • changedInput schema / properties / quantity / description
      Previous value: -""New value: +"Records wanted (1-100000). A real sample is returned now; the batch is quoted."
    • changedInput schema / properties / role / description
      Previous value: -""New value: +"Matches the job title as stated on the filing (e.g. 'Chief Executive', 'Chief Financial')."
    • removedInput schema / properties / seniority
      Removed value: -{
-  "description": "Director, VP, C-suite, etc.",
-  "type": "string"
-}
    • 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"
+}
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does disclose non-obvious traits: a real sample is returned on every call, pricing is on request, and no source provides a per-person LinkedIn URL. It also notes the data comes from the same two sources plus the filed entity record. It does not cover order placement or return format, but the disclosures go beyond 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.

Conciseness5/5

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

Two sentences front-load the core value proposition and then add commercial behavior and a key limitation. Every clause earns its place; there is no redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter tool with no output schema and no annotations, the description gives a solid high-level picture but leaves gaps: the 'two sources' are unnamed, the relationship to hsh-b2b-full is unaddressed, and order/quote mechanics are only hinted at. The schema fills parameter specifics, so the description is adequate but not fully complete.

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 baseline is 3; the description does not add parameter-level detail. It lists output fields rather than explaining input parameters, which is acceptable given the schema's thoroughness.

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 tool as the named-contacts product plus company-level attributes, enumerating specific fields such as industry, location, headcount, stage, ticker, exchange, state of incorporation, and entity type. It differentiates from the basic contact product, though it lacks an explicit action verb and refers to the sibling only as 'named-contacts product'.

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 'plus the company around the person' phrasing implies this is the choice when company context is needed, and the 'No LinkedIn URL' note sets an expectation boundary. However, it never explicitly names alternatives like hsh-b2b-contact or hsh-b2b-full, nor states when not to use this tool.

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