Skip to main content
Glama

HSH Data-on-Demand

by io.github.hshintelligence

hsh_subscribe_data_feed

FREE. Register a STANDING subscription so HSH watches for events matching your interest (e.g. SEC filings by form type and/or ticker/sector keywords) and sends you a quote the moment a match is caught. Turns one-off data buying into an always-on feed. Pay per matched delivery via x402.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
needNoPlain-language description of what to watch (e.g. 'any 8-K or 10-Q mentioning AAPL or semiconductors').
formsNoOptional SEC form types to match, e.g. ["8-K","10-Q"]. Omit to match any material form.
agent_idNoOptional agent/wallet id to associate with this subscription.
keywordsNoOptional tickers/company names/sector terms to match in the filing.
callback_urlNoOptional webhook URL to receive match notifications; omit to poll with hsh_check_subscription.
max_price_usdNoOptional max price per matched delivery; quotes above this are skipped.

TDQS

A3.6/5.0
Behavior3/5

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

No annotations provided, so the description carries the burden. It discloses that the tool is free to set up and pay-per-delivery via x402, and that it sends a quote on match. However, it omits details on subscription lifecycle, cancellation, and what happens when no match occurs.

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 fairly concise, front-loading the key value proposition and using a few sentences. It could be more structured but avoids unnecessary fluff.

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?

Given the 6 optional parameters and no output schema, the description provides the overall concept but doesn't explain the full workflow, such as how to manage subscriptions or what responses look like. It lacks references to sibling polling functions.

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%, with each parameter having a clear description. The tool description adds minimal extra meaning beyond the schema, providing context but not further clarifying parameter usage.

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 clearly states the tool's purpose: registering a standing subscription to monitor events (e.g., SEC filings) and receive quotes on match, turning one-off purchases into an always-on feed. It distinguishes from siblings by emphasizing the subscription aspect.

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 use for continuous monitoring rather than one-off buys but lacks explicit when-to-use or when-not-to-use comparisons with siblings like hsh_check_subscription. No alternatives or exclusions are mentioned.

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