noticed

account_status

Read-onlyIdempotent

Check connected accounts across the noticed browser extension and native iOS embedded-browser sessions. Use this to see whether GitHub and LinkedIn are connected, and whether LinkedIn and X imports are pairing, syncing, synced, partially synced, or need attention. Also lists your Teams (team_id, name, role, your share scope, member count) — the team_id to pass for scope:'team' reads.

Input Schema

Name	Required	Description	Default
No arguments

Output 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

A3.8/5.0

Behavior3/5

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

Annotations already declare this a safe, idempotent, non-destructive, closed-world read, so the description's main added value is enumerating the status vocabulary (pairing, syncing, synced, partially synced, need attention) and the platform scope of the check. That is genuinely useful, but it says nothing about staleness of the status, what triggers a re-check, or any auth prerequisites for seeing session-based data.

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?

Three sentences, front-loaded with the core purpose, then the status dimension, then the Teams payload. Dense but each sentence carries information; the only slack is the slightly rambling status list and the 'noticed' phrasing that adds nothing.

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?

For a parameterless read tool with an output schema and full annotation coverage, the description is close to self-sufficient: it frames the scope, the domain of results, and one cross-tool usage of the returned data. The one meaningful omission is disambiguation against the near-duplicate sibling get_connected_source_status.

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?

With zero parameters, the baseline is 4, and the description does a bit extra by explaining that the returned team_id is the value to supply elsewhere for scope:'team' reads, which ties this tool's output to other tools' parameters. No input semantics are needed here, so there is no gap to compensate for.

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 names a specific resource (connected accounts across the browser extension and iOS embedded-browser sessions) and enumerates what it reports: GitHub/LinkedIn connection state, LinkedIn/X import states, and a Teams listing. It is clear what the tool returns, but it never distinguishes itself from the very similarly named sibling get_connected_source_status, which an agent could easily confuse it with.

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 explicit usage framing ('Use this to see whether GitHub and LinkedIn are connected...') and adds a downstream purpose note that the returned team_id is what to pass for scope:'team' reads. It stops short of any exclusion guidance, so the overlap with get_connected_source_status and sync_connected_source is left unresolved.

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?