Skip to main content
Glama

Censtatd Hk

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds scoping detail (per user identifier) and pairing info, going beyond annotations.

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, front-loaded with primary action, no redundant words. Efficient and clear.

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?

Covers purpose, usage, scoping, and pairing with related tools. Single optional parameter and no output schema are acceptable given the tool's simplicity and annotation coverage.

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?

Input schema has 100% description coverage, already explaining the 'key' parameter. Description restates same meaning without adding additional detail beyond what schema provides.

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 the tool retrieves a saved value or lists all keys, using specific verb ('Retrieve', 'list') and resource ('value', 'keys'). Distinguishes from siblings 'remember' and 'forget'.

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?

Provides context for when to use (look up stored context to avoid re-deriving) and pairs with remember/forget. Does not explicitly state when not to use or compare to other sibling tools.

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

All Censtatd Hk 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

A4/5.0
Disambiguation4/5

Most tools target a distinct action or resource, and the long routing descriptions make choices like ask_pipeworx vs ask_pipeworx_grounded vs deep_research clear. The main weak spots are ask_pipeworx_beta being currently identical to ask_pipeworx and the six overlapping Polymarket tools, but each has a discernible workflow.

Naming Consistency3/5

Naming has internally consistent subfamilies such as censtatd_*, ask_pipeworx*, and polymarket_*, but overall it mixes verb-first names (get_table, validate_claim, subscribe), noun-first names (entity_profile, bet_research, pipeworx_feedback), and bare imperatives (remember, forget, recall). The set is readable but does not follow one convention.

Tool Count2/5

35 tools exceeds the 25+ threshold and feels heavy, especially since many tools (generate_llms_txt, scan_dependency, pipeworx_feedback, pipeworx_trending) are unrelated to the HK Census core implied by the server name. The broad Pipeworx scope explains the width, but the surface is still large for an agent to navigate efficiently.

Completeness4/5

For a read-only research/data-access gateway, coverage is strong: generic lookup, grounded verification, deep research, entity profile/compare/change, entity resolution, memory, and subscription lifecycle are all represented. Minor gaps exist, such as no subscription update, no explicit bulk/export path, and fewer HK C&SD convenience wrappers, but agents can work around them.

Resources