Skip to main content
Glama

Bridge status

grok_status
Read-onlyIdempotent

Checks whether the Grok Web bridge is ready by verifying Chrome extension connection, an open grok.com/imagine tab, and user login status.

Instructions

Bridge health: is the Chrome extension connected, is a grok.com/imagine tab open, is the user logged in.

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": "grok_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds real value beyond that by disclosing the exact diagnostic dimensions being probed (extension connectivity, tab presence, login state), which tells the agent what a failure would mean. It does not describe the shape of the response (booleans vs. a status string), which keeps it from a 5.

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 front-loaded sentence that labels the category ('Bridge health') and then enumerates the checks. No filler, no restatement of the title, nothing that could be cut.

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, idempotent diagnostic with no output schema, an agent needs only to know what is being checked and that it is safe to call repeatedly — both are supplied. The absence of return-format detail is a small gap, but nothing required to invoke the tool correctly 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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool is 4. Schema coverage is 100% and the empty object schema is unambiguous.

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 the resource (the bridge / Chrome-extension connection to grok.com) and enumerates the three concrete conditions it reports on: extension connected, imagine tab open, user logged in. That is far more specific than the bare name or the 'Bridge status' title, so an agent knows exactly what question this tool answers. It stops short of explicitly contrasting itself with siblings such as grok_usage or grok_settings, so it lands at 4 rather than 5.

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: an agent can infer this is a pre-flight/health check to run before grok_generate_image, grok_batch, or grok_generate_video, but the description never says 'call this first' or 'use this to diagnose failures.' There are no stated exclusions or named alternatives, so the routing decision is left to inference.

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