Skip to main content
Glama

Notification status

get_notification_status
Read-only

Check offline whether a login has an unacknowledged notification batch or uncertain delivery to resolve, without querying or acknowledging Librus notifications.

Instructions

Show whether a login has an unacknowledged notification batch or an uncertain delivery to resolve. Offline: it does not check Librus or acknowledge anything.

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": {
      "account_alias": "<account_alias>"
    },
    "name": "get_notification_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_aliasYesLogin alias from list_accounts.

Output Schema

NameRequiredDescriptionDefault
dataYes
has_pending_workYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.5.0
    • removedOutput schema / additionalProperties
      Removed value: -false
  2. Changed2 schema fields changedv2.3.1
    • addedInput schema / properties / account_alias / description
      Added value: +"Login alias from list_accounts."
    • changedInput schema / properties / account_alias / pattern
      Previous value: -"^(?:[^\\s\\x00-\\x1f\\x7f]|[^\\s\\x00-\\x1f\\x7f](?:[^\\s\\x00-\\x1f\\x7f]| )*[^\\s\\x00-\\x1f\\x7f])$"New value: +"^[^\\s\\x00-\\x1f\\x7f](?: *[^\\s\\x00-\\x1f\\x7f])*$"
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description adds genuinely new context by saying it makes no network call to Librus and mutates nothing, which is exactly the information an agent needs before a pre-write check. It says nothing about cost or freshness of the local state, though the output schema covers the return shape.

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 short sentences with no padding: the positive statement of purpose comes first, the scope limit second. Nothing is repeated.

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 one required param, full schema coverage, an output schema, and read-only annotations, the description covers what an agent needs. The only soft spot is the ambiguity of "uncertain delivery to resolve" — how the agent should act on a positive result isn't spelled out.

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?

The single parameter account_alias is fully documented in the schema (100% coverage), including that it comes from list_accounts. The description adds nothing about it, which is acceptable given the schema does the work, so baseline 3 applies.

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?

States a specific verb (show) and a specific resource state (unacknowledged notification batch / uncertain delivery to resolve) rather than just restating the name. An agent can tell this is a local status probe, not a fetch of new notifications.

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?

"Offline: it does not check Librus or acknowledge anything" draws a clear boundary against get_new_notifications and acknowledge_notifications. It stops short of naming those siblings explicitly, so the routing signal is implied rather than stated.

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