`get_notifications`

Read-only

Calls GET /api/notifications as the signed-in person · REST reference

The signed-in user's actionable notifications

Every piece of work currently waiting for the caller, newest first, derived on this request from live data — nothing is stored. Two sources contribute: each PENDING organization signup, to callers who can approve it (platform authority — the gate on POST /api/approvals/signups/{id}/approve), type ORGANIZATION; and each open payout clawback of a service provider, to callers holding hospital.clawbacks.request there, type CLAWBACK — NORMAL while it is under review, HIGH once it is approved and the clinic's payouts are paused. Any other caller gets an empty list. Each source's read runs on the caller's own bearer, so the DAL re-checks that authority from the graph.

Arguments

This tool takes no arguments.

Example call

A client sends this over the MCP session; Claude and other agents build it for you. The values are placeholders — the shape is real.

json

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

Result

On success (HTTP 200) the tool returns one text item holding the API's JSON, pretty-printed.

The caller's items; an empty list when nothing is waiting.

json

{
  "data": [
    {
      "actionUrl": "string",
      "createdAt": "2026-01-15T12:00:00Z",
      "id": "string",
      "message": "string",
      "priority": "LOW",
      "title": "string",
      "type": "ORGANIZATION"
    }
  ],
  "success": true
}

Fields

Field	Type	Description
`data`	array of object
`data[].actionUrl`	string	The portal route where the work is done, e.g. `/admin/approvals`.
`data[].createdAt`	string (date-time)	When the work arrived — for a signup, when it was submitted.
`data[].id`	string	Stable while the work is pending — `<source>:<subject id>`, e.g. `org-signup:<orgId>`.
`data[].message`	string
`data[].priority`	"LOW" \| "NORMAL" \| "HIGH" \| "URGENT"
`data[].title`	string
`data[].type`	"ORGANIZATION" \| "CLAWBACK"
`success`	true

When it fails

A failed call returns isError: true with the API's message as text.

403: Authenticated, but the caller holds none of the required permissions.

What the model is shown

This is the tool exactly as the server lists it in tools/list. The description starts with the REST call it makes.

json

{
  "name": "get_notifications",
  "description": "GET /api/notifications — Every piece of work currently waiting for the caller, newest first, derived on this request from live data — nothing is stored. Two sources contribute: each PENDING organization signup, to callers who can approve it (platform authority — the gate on `POST /api/approvals/signups/{id}/approve`), type ORGANIZATION; and each open payout clawback of a service provider, to callers holding `hospital.clawbacks.request` there, type CLAWBACK — NORMAL while it is under review, HIGH once it is approved and the clinic's payouts are paused. Any other caller gets an empty list. Each source's read runs on the caller's own bearer, so the DAL re-checks that authority from the graph.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true,
    "openWorldHint": false
  }
}