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
`organization`	No	the workspace this user is currently acting in
`setup_needed`	Yes	true when no Drive call can succeed until the user does something; see action
`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
`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. Dates show when Glama detected each change.

First observedSep 5, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, establishing a safe, non-mutating operation. The description adds meaningful behavioral context beyond annotations: it surfaces setup problems as clear statuses and disambiguates among multiple configured connectors. No contradiction exists between description and 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 three sentences with no filler. The primary purpose is front-loaded, followed by two sentences that add diagnostic context and a multi-connector edge case. Every sentence contributes information an agent needs.

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 parameterless, read-only diagnostic tool with an output schema, the description fully covers what the agent needs: the returned fields, the diagnostic role, and the multi-connector scenario. There are no missing prerequisites, side effects, or ambiguous edge cases.

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 0 parameters, so the description correctly needs no parameter-level explanations. Under the rubric, 0 params warrants a baseline score of 4. The schema fully covers the empty parameter set and the description adds no unnecessary parameter details.

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 uses a specific verb ('Report') and names the exact resource ('this user's ShareWatch setup status'), then enumerates the concrete items returned (email, workspace connection status, default folder, org membership, available actions). This clearly distinguishes it from the file-centric sibling tools, none of which provide connection or setup status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells when to use this tool: when setup problems need to be diagnosed, and notes that such problems appear here clearly rather than as confusing failures in other tools. It also provides a conditional use case for multiple connectors, specifying that this tool identifies the authenticated Google account.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?