Skip to main content
Glama

Hnb Hr

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.9/5.0
Behavior5/5

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

Annotations provide idempotentHint=true and destructiveHint=false; description adds key-value scoping by identifier, persistence details (authenticated vs. 24-hour anonymous), and pairing with other tools. No contradiction.

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?

Two sentences plus a short phrase, front-loaded with purpose, no wasted words. Every sentence adds essential information.

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 no output schema, description sufficiently explains storage behavior, scoping, and tool pairing, making it complete for a simple key-value store.

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 coverage is 100%, but description adds value by listing example keys (subject_property, target_ticker) and explaining value as any text, enhancing semantic understanding beyond schema.

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 saves data for later reuse, with concrete examples (resolved ticker, target address, user preference) and distinguishes from siblings recall and forget by mentioning pairing.

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

Usage Guidelines5/5

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

Explicitly says 'Use when you discover something worth carrying forward' and directs to recall and forget as alternatives for retrieval and deletion.

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