Skip to main content
Glama

HSH Data-on-Demand

by io.github.hshintelligence

hsh-web-scrape

Custom web scraping: extract structured data from any public site or directory. Handles static HTML, JS-rendered, paginated, and basic anti-bot. Pricing per record + complexity multiplier (1.0-2.5x). Tier 1: $3-15 (50 records). Tier 2: $15-500 (5K records). Tier 3: $250-3000 (100K).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsYesList of fields to extract per record.
quantityNoExpected record count (or 'all').
source_urlYesTarget site or section to scrape.
complexity_hintNo'static', 'js_render', 'auth_required'.

TDQS

B3.4/5.0
Behavior3/5

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

Discloses handling capabilities and pricing tiers, but lacks details on rate limits, authentication, error handling, or legal considerations.

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?

Three sentences, front-loaded with purpose. Pricing details add length but are relevant. No unnecessary information.

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?

Lacks details on supported output formats, turnaround time, and limitations. Given the complexity of web scraping and no output schema, more completeness would be beneficial.

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 covers all parameters with descriptions; the tool description adds context on complexity multipliers and tiers, but doesn't significantly enhance parameter meaning.

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?

Description clearly states extracting structured data from public sites, handling various page types. Distinguishes from sibling tools focused on specific datasets.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this vs. alternatives like pre-built datasets. Pricing info is useful but doesn't clarify selection criteria.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0
Disambiguation4/5

Most tools have distinct purposes, but some closely related tools (e.g., hsh-b2b-*, hsh-esg-* variants) could cause confusion. Descriptions help differentiate, but an agent might still misselect similar products.

Naming Consistency3/5

Naming convention is mixed: some tools use hyphens (hsh-b2b-contact), others use underscores (hsh_broker_data_request). While mostly readable, the inconsistency could be confusing for agents expecting a uniform pattern.

Tool Count3/5

32 tools is on the high side for a single server, but given its purpose as a data marketplace, the large number reflects a wide catalog. However, it may be overwhelming for agents to navigate.

Completeness3/5

Covers many data domains but has obvious gaps (e.g., weather, social media). The inclusion of custom data request tools (hsh_describe_data_need, hsh_broker_data_request) mitigates these gaps, allowing agents to request missing data.

Resources