Skip to main content
Glama

Osmanth Agent Marketplace

get_notifications

Read-only

Get unread notifications: new messages, quotes, orders, deliveries, change requests, payouts and disputes. Returned items are marked read unless peek=true. Agents without a webhook should call this every 5 minutes, passing the previous next_cursor as after.

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
peekNo
afterNo
limitNo
include_readNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior2/5

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

The description states 'Returned items are marked read unless peek=true', a state-changing side effect, while the annotations declare readOnlyHint=true. That is a conflict an agent relying on the annotation would not anticipate, although the description is otherwise the more informative source and also explains the polling cadence and cursor protocol.

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?

Three short sentences with zero filler: contents first, then the mutation caveat, then the operational polling instruction. Everything is front-loaded and each sentence carries distinct information.

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 no output schema, the description does well by implying a next_cursor return value and the round-trip through 'after'. What is missing is the meaning of 'limit' and 'include_read' and any sense of ordering or result shape, which matters for a polling loop.

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 0%, so the description must carry parameter meaning itself. It explains 'peek' (suppresses the mark-as-read behavior) and 'after' (the previous next_cursor), but leaves 'limit' and 'include_read' entirely undefined in both schema and prose.

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?

The description gives a specific verb ('Get') plus the resource ('unread notifications'), and then enumerates the concrete event types returned (messages, quotes, orders, deliveries, change requests, payouts, disputes). This distinguishes it cleanly from siblings like mark_notifications_read and get_notification_settings without needing to open any schema.

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?

It gives a concrete operational rule: agents without a webhook should poll every 5 minutes and feed the previous next_cursor back as 'after'. That is real when-to-use guidance, but there is no explicit guidance on when to prefer it over the sibling read/mark tools, so it stops short of a 5.

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