Skip to main content
Glama

Read notifications

get_notifications
Idempotent

Read your notifications (order fills, mission results, combat and system messages), newest first. By default only unread ones (note: get_status already marks the notifications it shows as read; pass unread_only=false to read them again). Read-only unless mark_read=true, which marks the returned ones as read (unread_total = still unread after this call, i.e. without the ones just marked). Returns a list with type, text and timestamp; check it after place_orders or mission work.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1-50, default 20
bearerNoYour SPACE-CORE Bearer token. Only needed if your client cannot send the Authorization header.
mark_readNoMark the returned notifications as read (default false)
unread_onlyNoOnly unread (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / bearer / description
      Added value: +"Your SPACE-CORE Bearer token. Only needed if your client cannot send the Authorization header."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and idempotentHint=true; the description earns credit by clarifying that the tool is read-only *unless* mark_read=true, and that unread_total excludes the records just marked. Remaining gap: the description implicitly makes repeat calls with mark_read=true non-idempotent, which sits in mild tension with idempotentHint=true and is not reconciled. Not a contradiction, since the conditional mutation matches readOnlyHint=false.

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?

Front-loaded with purpose and order, then defaults, then the mutation caveat, then the return shape — a sensible priority order with no filler sentences. The nested parentheticals around get_status and unread_total make it denser than it needs to be, costing a point on readability.

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?

There is no output schema, so the description carries the return contract and does so ('a list with type, text and timestamp'), plus it defines the otherwise-undocumented unread_total semantics. Combined with the conditional-mutation caveat and the get_status interaction, an agent has everything needed to call it correctly.

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?

Schema description coverage is 100%, so both mark_read and unread_only are already documented at the field level, and the description largely restates them. It does add motive beyond the schema for unread_only=false (get_status already consumed the unread set), which is the main value-add; limit and bearer get no additional treatment beyond what the schema says.

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 and resource ('Read your notifications') and enumerates what is returned (order fills, mission results, combat and system messages) plus the sort order ('newest first'). It also distinguishes itself from the sibling get_status by explaining that get_status already marks shown notifications read, so an agent can tell the two apart without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance ('check it after place_orders or mission work'), names the alternative that affects behavior (get_status), and gives the precise condition for the non-default path ('pass unread_only=false to read them again'). Both the default and the override case are covered.

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