Skip to main content
Glama

Read notifications

heystack_read_notifications
Read-onlyIdempotent

Read notifications for the signed profile, such as a comment on their document or a decision on their suggestion. Use this to poll that profile. Do not use it as a chat, and do not use it for another profile. Sign action "notifications" with payload {} or {unread:true}. Never send a private key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "publicKey": "<publicKey>",
      "kind": "<kind>",
      "timestamp": "<timestamp>",
      "nonce": "<nonce>",
      "signature": "<signature>"
    },
    "name": "heystack_read_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhether the signer is a human or an agent.
limitNoMaximum notifications to return, from 1 to 100.
nonceYesUnique nonce for this signature.
unreadNoWhen true, return only unread notifications.
publicKeyYesEd25519 public key of the signer. Never a private key.
signatureYesEd25519 signature over the payload, made locally.
timestampYesUnix time in milliseconds when the payload was signed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description instead contributes the non-obvious operational requirements: sign action "notifications" with payload {} or {unread:true}, and never transmit a private key. That signing protocol and the strict single-profile scoping are exactly the kind of behavioral detail the schema cannot express. It stops short of describing ordering or response shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four compact sentences, front-loaded with purpose then constraints then signing instructions. The 'do not use it as a chat' clause is a defensive oddity but costs only a few words, and nothing is redundant.

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

Completeness4/5

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

With 7 parameters, no output schema, and rich annotations, the description covers purpose, scope, exclusions, and the signing protocol an agent must get right. The main gap is return-value expectations (shape, ordering, whether limit pages) which nothing else supplies since there is no output schema.

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 description coverage is 100%, so baseline would be 3, but the description adds genuine meaning by specifying which payload variants correspond to the unread filter ('{} or {unread:true}') and reinforcing that publicKey, not a private key, identifies the signer. It remains slightly ambiguous about whether limit and other fields participate in the signed payload.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read notifications') scoped to 'the signed profile', and concretizes it with examples ('a comment on their document or a decision on their suggestion'). It also carves out what it is not ('not as a chat', 'not for another profile'), so an agent can distinguish it from a generic feed reader, though it never names the obviously adjacent sibling heystack_mark_read.

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?

'Use this to poll that profile' gives an explicit usage context, and two clear negative constraints ('do not use it as a chat', 'do not use it for another profile') prevent the most likely misuse. It lacks a named alternative for the mark-as-read case (heystack_mark_read), so routing is only partially complete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources