noticed

account_status

Read-onlyIdempotent

Check connected accounts across the noticed browser extension and native iOS embedded-browser sessions. Use this to see whether LinkedIn and X are connected, pairing, syncing, synced, partially synced, or need attention.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether noticed completed the operation.
`data`	No	The operation result when ok is true.
`error`	No	A human-readable error when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 26, 2026

addedOutput schema / properties / data / properties / extension

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "paired": {
+      "type": "boolean"
+    },
+    "ready": {
+      "type": "boolean"
+    },
+    "sources": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "error": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "itemCount": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "label": {
+            "enum": [
+              "LinkedIn",
+              "X"
+            ],
+            "type": "string"
+          },
+          "requiredDataReady": {
+            "type": "boolean"
+          },
+          "source": {
+            "enum": [
+              "linkedin_extension",
+              "x_extension"
+            ],
+            "type": "string"
+          },
+          "status": {
+            "enum": [
+              "pairing",
+              "syncing",
+              "synced",
+              "not_signed_in",
+              "needs_attention",
+              "partial"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "source",
+          "label",
+          "status",
+          "requiredDataReady",
+          "itemCount",
+          "error"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "status": {
+      "enum": [
+        "not_started",
+        "pairing",
+        "syncing",
+        "ready",
+        "needs_attention"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "paired",
+    "ready",
+    "status",
+    "sources"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "description": "The operation result when ok is true.",
+      "properties": {
+        "actions": {
+          "additionalProperties": true,
+          "properties": {},
+          "type": "object"
+        },
+        "chat": {
+          "$ref": "#/properties/data/properties/github"
+        },
+        "github": {
+          "additionalProperties": true,
+          "properties": {
+            "connected": {
+              "type": "boolean"
+            },
+            "displayValue": {
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "required": [
+            "connected"
+          ],
+          "type": "object"
+        },
+        "gmail": {
+          "additionalProperties": false,
+          "properties": {
+            "connected": {
+              "type": "boolean"
+            },
+            "imported": {
+              "type": "boolean"
+            }
+          },
+          "required": [
+            "connected",
+            "imported"
+          ],
+          "type": "object"
+        },
+        "linkedin": {
+          "$ref": "#/properties/data/properties/github"
+        },
+        "linkedinExport": {
+          "additionalProperties": true,
+          "properties": {
+            "imported": {
+              "type": "boolean"
+            },
+            "lastImportedAt": {
+              "$ref": "#/properties/data/properties/github/properties/displayValue"
+            }
+          },
+          "required": [
+            "imported",
+            "lastImportedAt"
+          ],
+          "type": "object"
+        },
+        "nextAction": {
+          "type": "string"
+        },
+        "teams": {
+          "items": {
+            "$ref": "#/properties/data/properties/actions"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "error": {
+      "description": "A human-readable error when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether noticed completed the operation.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

First observedAug 22, 2026

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, idempotentHint=true, and destructiveHint=false, so the safe read-only nature is covered. The description adds useful behavioral context by listing the possible connection/sync states and specifying the two session contexts (browser extension and iOS embedded-browser), which goes beyond the annotations without contradicting them.

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?

The description is two sentences with no filler. The action ('Check connected accounts') is front-loaded, followed immediately by the intended use case and the specific statuses. Every clause earns its place.

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?

For a zero-parameter, read-only status check with an output schema present, the description is fully sufficient. It states what is checked, which platforms are covered, and the kinds of states the agent should look for, so no critical information is missing.

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?

The tool has zero parameters, so there is no parameter semantics burden on the description. A score of 4 is the baseline for a no-parameter tool, and the description does not need to compensate for any schema gaps.

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?

The description uses a specific verb ('Check') and resource ('connected accounts across the noticed browser extension and native iOS embedded-browser sessions'), and it names the specific platforms (LinkedIn and X). It is clear in what it does, but it does not explicitly distinguish itself from the similar sibling tool 'get_connected_source_status', which may be the per-source counterpart.

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?

The description includes an explicit usage directive: 'Use this to see whether LinkedIn and X are connected, pairing, syncing, synced, partially synced, or need attention.' This tells the agent when to invoke it, but it does not mention when not to use it or mention alternatives like 'get_connected_source_status' or 'sync_connected_source'.

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

All noticed tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?