@helloaigent-dev/publisher
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HELLOAIGENT_API | No | API base URL (default https://api.helloaigent.dev) | https://api.helloaigent.dev |
| HELLOAIGENT_TOKEN | No | Publish token (a feed's publisher token, or the admin token); falls back to the admin token | |
| HELLOAIGENT_ADMIN_TOKEN | Yes | Admin token; required for feed management and analytics |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hello_aigent_create_feedA | Create a Hello Aigent feed (a stream agents subscribe to). Mints an Ed25519 signing keypair and a per-feed publisher token, and returns the generated discovery file. The publisher token is shown ONCE — save it; it authorizes publishing to this feed. Requires the admin token. |
| hello_aigent_list_feedsA | List the feeds you own (id, title, topics, latest_seq, discovery URL). Requires the admin token. |
| hello_aigent_publishA | Publish a signed update to a feed. The server Ed25519-signs the envelope; subscribed agents verify it before acting. Uses the feed's publisher token (or the admin token). IMPORTANT: publishing sends to every subscriber — confirm the content with the feed owner before calling. |
| hello_aigent_report_eventA | Report an action outcome for a subscription — the "acted" signal that powers the analytics funnel. Call this after a subscriber's agent completes one of your callable actions. Uses the feed's publisher token (or the admin token). |
| hello_aigent_overviewA | Overview for a feed: subscribers, fetches today, 7-day return rate, signed-update count, a fetch sparkline, and recent agent-attributed activity. Requires the admin token. |
| hello_aigent_funnelA | The subscribed → returned → acted cohort funnel for a feed over a window, with return-rate and act-rate. Requires the admin token. |
| hello_aigent_event_logA | Filterable audit of feed events (subscribe/fetch/action/unsubscribe), newest first, agent-attributed. Requires the admin token. |
| hello_aigent_subscribersB | The feed's subscriber list — the audience you own: agent, principal, topics, consent scope, last fetch, and status (active/dormant/revoked). Requires the admin token. |
| hello_aigent_discovery_fileA | Get the generated discovery file (hello-aigent.json) for a feed — host it at your site's /.well-known/hello-aigent.json so agents can find and subscribe. Public; no token needed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct resource or action: feed creation, listing, publishing, event reporting, subscriber data, event log, analytics overview, funnel, and discovery file. There is no overlap or ambiguity between them.
All tools share the hello_aigent_ prefix, which provides strong consistency. However, the second part mixes noun-only names (event_log, subscribers, overview, funnel, discovery_file) with verb_verb_noun patterns (create_feed, list_feeds, report_event), making the convention slightly inconsistent.
Nine tools is well within the ideal 3-15 range and each tool serves a clear, non-redundant purpose for a feed management and analytics domain. The count feels appropriate and not bloated.
The tool set covers the core lifecycle of a feed: creation, publishing, event reporting, and analytics (overview, funnel, subscribers, event log). Minor gaps exist such as feed deletion or metadata update, but these are not critical to the primary publisher workflow.