ShareWatch

Connection Status

get_status

Read-onlyIdempotent

Report this user's ShareWatch setup status: the authenticated user's email, workspace connection status, default folder, org membership, and available actions. Setup problems surface here as a clear status, whereas they surface in other tools as unrelated-looking failures. When multiple ShareWatch connectors are configured, this identifies which Google account this connector is authenticated as.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`action`	No	present only when the user must do something; absent means nothing is required of them
`diagram`	No	ASCII sketch of which of the two links is broken; reproduce it verbatim or not at all
`message`	No	detail about a problem, when there is one
`summary`	Yes	one sentence covering both identities and the health, written to be paraphrased to the user
`user_name`	No
`tool_count`	Yes	how many tools this server implements right now
`user_email`	No	the ShareWatch account the caller is signed in to, which may differ from the connected Google account
`connections`	No	the accounts this user has connected, primary first; absent when none
`files_shared`	Yes	how many files are currently shared with ShareWatch across every connected account; 0 with has_shared_before true means they took them all back, not that they never started
`organization`	No	the workspace this user is currently acting in
`setup_needed`	Yes	true when the user must do something before the agent can work with their files — Google is not linked, or it is linked and they have never shared a file; see action. Creating a NEW file still works in the second case
`default_folder`	No	where new files land when no parent is given; absent when none is set
`schema_version`	Yes	bump this and a client with a cached tool list will see the old value — the crudest possible staleness check
`available_tools`	Yes	every tool the SERVER implements — NOT the tools this caller may invoke, and not a permissions list. Compare it against your own visible tool list: if yours is shorter, your client is holding a cached list and the user must refresh the connector.
`connection_health`	Yes	'ok' (a token was minted just now), 'never_connected' (Google Workspace was never linked), 'revoked' (the Google grant is gone — reconnecting the MCP connector will NOT fix it), or 'degraded' (still connected, but the last token refresh failed)
`folder_suggestion`	No	advice to relay when no default folder is configured
`has_shared_before`	Yes	whether the user has EVER shared a file — false is the first encounter, and setup_needed says what to do
`workspace_connected`	Yes	whether ShareWatch can reach the user's Google Drive at all
`google_drive_identity`	No	the Google account whose Drive is actually connected — say this out loud when it differs from user_email, because file operations land in THIS account

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

addedOutput schema / properties / action / properties / first_action

Added value: +{
+  "description": "something you can do for the user immediately, with no setup — offer it before relaying the steps",
+  "type": "string"
+}

Changed3 schema fields changedSep 11, 2026

addedOutput schema / properties / files_shared

Added value: +{
+  "description": "how many files are currently shared with ShareWatch across every connected account; 0 with has_shared_before true means they took them all back, not that they never started",
+  "type": "integer"
+}

addedOutput schema / properties / has_shared_before

Added value: +{
+  "description": "whether the user has EVER shared a file — false is the first encounter, and setup_needed says what to do",
+  "type": "boolean"
+}

changedOutput schema / required

Previous value: -[
-  "schema_version",
-  "tool_count",
-  "available_tools",
-  "workspace_connected",
-  "connection_health",
-  "setup_needed",
-  "summary"
-]New value: +[
+  "schema_version",
+  "tool_count",
+  "available_tools",
+  "workspace_connected",
+  "connection_health",
+  "setup_needed",
+  "summary",
+  "files_shared",
+  "has_shared_before"
+]

Changed1 schema field changedSep 11, 2026

addedOutput schema / properties / connections

Added value: +{
+  "description": "the accounts this user has connected, primary first; absent when none",
+  "items": {
+    "properties": {
+      "account": {
+        "description": "the account's address",
+        "type": "string"
+      },
+      "primary": {
+        "description": "where new files land unless a create tool names another account",
+        "type": "boolean"
+      },
+      "provider": {
+        "description": "google",
+        "type": "string"
+      }
+    },
+    "required": [
+      "account",
+      "provider",
+      "primary"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

Changed7 schema fields changedSep 10, 2026

removedOutput schema / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / action / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / default_folder / additionalProperties
```
Removed value: -false
```

removedOutput schema / properties / files_shared

Removed value: -{
-  "description": "how many files the user has shared with ShareWatch right now. Zero does not mean the Drive is empty; it means the agent can see nothing",
-  "type": "integer"
-}

removedOutput schema / properties / has_shared_before

Removed value: -{
-  "description": "whether this user has ever shared a file with ShareWatch. False on a healthy connection is the first encounter: they connected an agent and have not yet learned that files must be picked, and action carries the link. True with files_shared zero is a user who knows the routine and currently has nothing shared",
-  "type": "boolean"
-}

changedOutput schema / properties / setup_needed / description

Previous value: -"true when the user must do something before the agent can work with their files — Google is not linked, or it is linked and nothing is shared yet; see action. Creating a NEW file still works in the second case"New value: +"true when the user must do something before the agent can work with their files — Google is not linked, or it is linked and they have never shared a file; see action. Creating a NEW file still works in the second case"

changedOutput schema / required

Previous value: -[
-  "schema_version",
-  "tool_count",
-  "available_tools",
-  "workspace_connected",
-  "connection_health",
-  "setup_needed",
-  "files_shared",
-  "has_shared_before",
-  "summary"
-]New value: +[
+  "schema_version",
+  "tool_count",
+  "available_tools",
+  "workspace_connected",
+  "connection_health",
+  "setup_needed",
+  "summary"
+]

Changed4 schema fields changedSep 10, 2026

addedOutput schema / properties / files_shared

Added value: +{
+  "description": "how many files the user has shared with ShareWatch right now. Zero does not mean the Drive is empty; it means the agent can see nothing",
+  "type": "integer"
+}

addedOutput schema / properties / has_shared_before

Added value: +{
+  "description": "whether this user has ever shared a file with ShareWatch. False on a healthy connection is the first encounter: they connected an agent and have not yet learned that files must be picked, and action carries the link. True with files_shared zero is a user who knows the routine and currently has nothing shared",
+  "type": "boolean"
+}

changedOutput schema / properties / setup_needed / description

Previous value: -"true when no Drive call can succeed until the user does something; see action"New value: +"true when the user must do something before the agent can work with their files — Google is not linked, or it is linked and nothing is shared yet; see action. Creating a NEW file still works in the second case"

changedOutput schema / required

Previous value: -[
-  "schema_version",
-  "tool_count",
-  "available_tools",
-  "workspace_connected",
-  "connection_health",
-  "setup_needed",
-  "summary"
-]New value: +[
+  "schema_version",
+  "tool_count",
+  "available_tools",
+  "workspace_connected",
+  "connection_health",
+  "setup_needed",
+  "files_shared",
+  "has_shared_before",
+  "summary"
+]

First observedSep 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds valuable behavioral context beyond annotations: it explains that setup problems are reported clearly here versus surfacing as unrelated failures elsewhere, and that it identifies which account the connector uses when multiple are configured. No contradiction with annotations.

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 well-structured and concise. It front-loads the core purpose, lists the reported fields, then explains the diagnostic value and the multi-connector behavior. Each sentence contributes meaningfully with no filler or repetition.

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?

Given zero parameters, an output schema, and safety annotations, the description is complete. It covers what the tool reports, why it's useful for troubleshooting, and the edge case of multiple connectors. No critical information is missing for an agent to call it correctly.

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 the schema provides no parameter semantics. The baseline for 0 parameters is 4, and the description doesn't need to add parameter details. It appropriately focuses on the tool's purpose and output.

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 states a specific verb ('Report') and resource ('ShareWatch setup status') and lists the exact fields returned (email, connection status, default folder, org membership, available actions). It also distinguishes itself from sibling tools by explaining that setup problems surface here clearly rather than as unrelated failures, making its purpose unambiguous.

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 provides clear context on when to use this tool: to diagnose setup issues and identify the authenticated Google account when multiple connectors exist. It contrasts its behavior with other tools ('whereas they surface in other tools as unrelated-looking failures'), which implies when to prefer it, though it lacks an explicit 'use this instead of X' exclusion.

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

All ShareWatch 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?