Skip to main content
Glama

HSH Data-on-Demand

by io.github.hshintelligence

hsh-shariah-screen

Rule-based Shariah (Islamic finance) compliance screen for US-listed companies. Applies AAOIFI-style screening using authoritative SEC financials: (1) business-activity screen (flags alcohol, tobacco, gambling, conventional banking/insurance, pork, weapons, adult), (2) financial ratio screens (debt/assets <33%, liquid+interest/assets <33%, receivables/assets <49%). Returns verdict (compliant / non_compliant / questionable) with the exact failing test and ratios. Pay per call via x402 (USDC on Base).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesUS-listed ticker to screen, e.g. AAPL, XOM, JPM.

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the output (verdict with failing test and ratios) and payment model, but lacks details on data freshness, rate limits, or authentication.

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?

Three sentences, each serving a purpose: purpose definition, screening criteria, and output/payment. No redundancy or unnecessary details.

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?

Explains methodology, output, and payment. Missing minor details like data update frequency or whether the screener is real-time. Still fairly complete given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'ticker' has a schema description with examples (AAPL, XOM, JPM) and context of US-listed. This adds value beyond the schema, which already provides type and required status.

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?

Clearly states it is a Shariah compliance screen for US-listed companies, detailing the screening criteria (business-activity and financial ratios). This distinguishes it from sibling tools, none of which offer shariah screening.

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?

Implied usage for shariah compliance screening of US equities. No explicit when-to-use vs alternatives or when-not-to-use. The payment note is a requirement, not a guideline.

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