Skip to main content
Glama

hsh-company-intelligence

Real-time intelligence on a company by name or domain. ALWAYS returns: profile, description, industry, tech stack detected on the live site, and public social links; and, where they can be found, its SEO description (seo_description), logo and specialties. Each of description, logo and specialties carries a *_source naming where it came from, and says so when a language model wrote or extracted it from the site's text. For Y Combinator companies, founders, batch, tags and the YC page are added from the YC company listing (served from a copy dated 14 Apr 2026 while the hosted one is down); names the listing puts on several companies are labelled, since they may be partners or investors. Every response states which path served it in source_path, and a live-hunt-only response lists what it could not provide. discover (a filtered list of YC companies) answers from the same listing. Pay per call via x402 (USDC on Base).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "hsh-company-intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
limitNo
queryYesCompany name or domain, OR a discovery query.
filtersNoFor discover: { industry?, batch?, is_hiring? }. No contact-detail filter exists: this product collects no email addresses (removed at source 2026-09-10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / filters / description
      Previous value: -"For discover: { industry?, batch?, is_hiring?, has_email? }"New value: +"For discover: { industry?, batch?, is_hiring? }. No contact-detail filter exists: this product collects no email addresses (removed at source 2026-09-10)."
  2. Changed3 schema fields changed
    • changedInput schema / properties / filters / description
      Previous value: -"For discover: { industry?, batch?, is_hiring?, has_email? }."New value: +"For discover: { industry?, batch?, is_hiring?, has_email? }"
    • changedInput schema / properties / limit / description
      Previous value: -"Max results for discover mode."New value: +""
    • changedInput schema / properties / mode / description
      Previous value: -"lookup = one company; discover = filtered list."New value: +""
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the pay-per-call x402/USDC billing model, that responses report a `source_path`, that the YC data is served from a stale local copy (dated 14 Apr 2026), that some listed names may be partners or investors, and that a live-hunt-only response enumerates its own gaps. It still omits failure modes, rate limits, and whether repeat calls are billed each time, so it stops short of a 5.

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

Conciseness3/5

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

The main purpose is front-loaded and most sentences carry real information, but the middle is a dense run-on: the '*_source' provenance sentence and the YC-copy parenthetical are convoluted and require re-reading. Structure is a single undifferentiated paragraph mixing cost, provenance, and return shape.

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?

There is no output schema, and the description compensates by enumerating the returned fields (profile, description, industry, tech stack, social links, seo_description, logo, specialties, YC founders/batch/tags) plus provenance and staleness caveats. For a 4-parameter tool of this complexity the only real gaps are `limit` semantics and error behavior.

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 50%, with `mode` and `limit` carrying empty descriptions. The prose partially compensates by explaining what discover returns and that no contact-detail filter exists, but it never explains `limit`, the default mode, or how `query` is interpreted differently in discover versus lookup. Baseline 3 for partial coverage with partial compensation.

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 opening sentence names the resource (company) and the two lookup keys (name or domain), and later states the second mode ('discover (a filtered list of YC companies)'), so an agent can tell what the tool returns. It does not differentiate itself from the nearby hsh-b2b-* company tools, leaving the agent to infer which company endpoint to pick.

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?

Usage is implied rather than stated: lookup by name/domain, or pass a discovery query to get a filtered YC list. There is no explicit when-to-use/when-not-to-use guidance and no named alternative among the sibling tools, so an agent must infer the selection rule from the data-shape descriptions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources