Skip to main content
Glama

Hnb Hr

by io.github.pipeworx-io

Pipeworx Trending

pipeworx_trending
Read-onlyIdempotent

What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking your own question, (3) seeing whether your use case aligns with what most agents need. Self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count). Cached 5min-1h depending on window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNo24h (default) | 7d | 30d. Shorter windows surface what's hot right now; longer windows show steady-state demand.

TDQS

A4.7/5.0
Behavior5/5

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

Description adds significant context beyond annotations: caching behavior (5min-1h), data source (CF analytics), privacy (no PII), and derived nature. Annotations already indicate readOnly, openWorld, idempotent, non-destructive.

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?

Description is well-structured: a concise one-liner followed by bullet-point use cases and technical details. Every sentence adds value without redundancy.

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

Completeness5/5

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

Given the tool's simplicity (one optional parameter, no output schema), the description fully covers what the tool returns, its source, caching, and privacy. No gaps.

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?

Schema covers window parameter with enum and description. The description adds semantic value by explaining the trade-off between hotness and steady-state demand for different window lengths.

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 that the tool returns trending tools, packs, and call volume from other agents. It distinguishes from siblings like 'discover_tools' by focusing on real-time popularity.

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

Usage Guidelines4/5

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

Three explicit use cases are listed, providing clear context for when to use the tool. However, it does not mention when not to use it or suggest alternatives.

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

All Hnb Hr 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

A3.7/5.0
Disambiguation2/5

Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical (beta is currently identical to ask_pipeworx), and deep_research and validate_claim also overlap with the ask_pipeworx family. The Polymarket tools are more distinct, but the query family creates real ambiguity.

Naming Consistency2/5

Tool names mix leading verbs (ask_, compare_, resolve_, scan_) with leading nouns (entity_profile, recent_changes, hnb_currency_rate) and there are multiple subfamily prefixes (ask_pipeworx_*, polymarket_*, hnb_*). All are snake_case, but no consistent verb_noun or noun pattern is followed.

Tool Count2/5

33 tools is well above the 25+ threshold, and the server name ('Hnb Hr') implies a narrow Croatian banking scope while the majority of tools are for a broad data research platform. Many meta-tools (discover_tools, suggest_questions, pipeworx_feedback, pipeworx_trending) inflate the count beyond what the apparent purpose needs.

Completeness3/5

The HNB currency functionality is complete (single and all rates, historical and latest), and the broader data platform offers good coverage via the ask_pipeworx router, subscriptions, and memory tools. However, there are gaps (no direct HNB news or historical archive tool, patents soft-fail, and out-of-domain tools like generate_llms_txt), and the mismatch between server name and content leaves the surface feeling incomplete.

Resources