hello-aigent-subscriber
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HELLO_AIGENT_STATE | No | Override the state file location (default: ~/.hello-aigent/subscriptions.json) |
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_subscribeA | Subscribe to a Hello Aigent feed. Fetches the site's discovery file (/.well-known/hello-aigent.json), picks the feed, and subscribes on behalf of a principal (the account/user this agent acts for). IMPORTANT: subscribing is a consent decision — confirm with your principal before calling. Returns the stored subscription (token is persisted locally, not shown). |
| hello_aigent_fetchA | Fetch new updates for a subscription (only-new-since via the stored cursor). Every envelope is signature-verified against the feed's public key; verified updates are returned under |
| hello_aigent_unsubscribeA | Unsubscribe (revoke consent) for a subscription. Idempotent — safe to call twice. |
| hello_aigent_list_subscriptionsA | List locally stored Hello Aigent subscriptions (active and revoked) with feed, principal, consent scope, and cursor. Tokens are never returned. |
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 4 tools
Each tool has a clearly distinct purpose: subscribing, listing, fetching updates, and unsubscribing. There is no overlap or ambiguity between them.
All tool names follow the same 'hello_aigent_[verb]' pattern, using snake_case consistently. The verbs are descriptive and appropriate.
Four tools is well-scoped for a subscription management server. Each tool serves a fundamental operation (subscribe, list, fetch, unsubscribe) without being excessive or insufficient.
The tool set covers the full lifecycle of a subscription: subscribing, listing subscriptions, fetching updates, and unsubscribing. There are no missing operations for this domain.