Skip to main content
Glama

Grok bridge diagnostics

grok_status
Read-onlyIdempotent

Check Grok Build setup without using quota when a call reports 'not found'; verify Grok version, auth, model list, data location, and flag newer agent-intern releases.

Instructions

Check the Grok Build setup (EXPERIMENTAL). Spends no quota; run it first when a call says "not found". Its bridge version row says when a newer agent-intern release is out: if so, tell the user. Also checks grok's version, auth and model list (both from grok models, which answers even when logged out), and where grok keeps its data. Green means the setup looks right, not that a live answer was ever confirmed.

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

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, not open-world), yet the description still adds real value: zero quota cost, that `grok models` answers even when logged out, and the important caveat that 'green means the setup looks right, not that a live answer was ever confirmed.' Disclosing that limitation prevents an agent from over-reading a passing result.

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?

Front-loaded with the verb, resource, and EXPERIMENTAL flag, followed by trigger, follow-up, and caveat in a tight sequence with no filler. The prose is dense — heavy backticked row names and a packed third sentence — but nothing is redundant.

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 diagnostic with an output schema, the description need not explain return shapes, and it instead explains how to read the result and what action to take. Everything an agent needs to decide whether and when to run it is present.

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 no parameters, so the baseline is 4 and there is nothing further for the description to disambiguate. Schema coverage is 100% and the description correctly spends no words on inputs.

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?

States a specific verb and resource ('Check the Grok Build setup') and then enumerates exactly what it inspects: bridge version, grok version, auth, model list, and data location. That detail separates it cleanly from the grok_ask/grok_continue siblings, which drive live calls rather than diagnose setup.

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?

Gives a concrete trigger — 'run it first when a call says "not found"' — and a follow-up directive to tell the user when the bridge version row shows a newer release. It does not state when to skip this tool or name a competing diagnostic alternative, which keeps it just short of a 5.

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