Skip to main content
Glama

Bridge Status

bridge_status

Checks the bridge version and connected Google account, and confirms whether Drive is enabled for creating and editing Apps Script projects.

Instructions

Check the bridge: its version, the Google account it runs as, and whether the Drive service is enabled (needed to create and edit projects).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the diagnostic surface (version, identity, Drive enablement) and why the Drive flag matters, but does not say whether the call is strictly read-only, whether it can trigger an auth handshake, or how it behaves when the bridge is unreachable.

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?

A single sentence, front-loaded with the verb and resource, and every clause adds information an agent needs (the three status fields plus the reason the Drive flag matters). Nothing is padding.

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?

With zero parameters, an output schema already documenting return values, and no annotations to reconcile, the description covers what an agent needs to decide to call it. The only shortfall is the missing explicit trigger condition for when a status check is warranted.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The empty schema is consistent with the described no-argument status check.

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?

States a specific verb and resource ('Check the bridge') and enumerates the exact facts returned: version, the Google account it runs as, and Drive service enablement. That is far more specific than the title alone, though it does not explicitly contrast itself with the action-oriented siblings (create_project, run_code, etc.), which it only implicitly differs from by being a diagnostic.

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

Usage Guidelines3/5

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

Usage is only implied: the parenthetical '(needed to create and edit projects)' hints that this is a pre-flight check before project creation or editing, but the description never says when to call it, when not to, or names any alternative to consult instead. An agent must infer the trigger condition.

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