Skip to main content
Glama

Claude Code bridge diagnostics

claude_status
Read-onlyIdempotent

Verifies Claude Code setup without spending quota by checking version, sign-in status, session location, and bridge version to diagnose "not found" errors.

Instructions

Check the Claude Code setup, for hosts other than Claude Code. 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 claude's version (2.1.259+ needed), how you're signed in (claude auth status; account details are left out), and where Claude Code keeps its sessions.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.37.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety is covered structurally. The description adds behavior annotations do not: zero quota consumption, a privacy guarantee ("account details are left out"), and a version prerequisite (2.1.259+). It does not describe failure modes or latency, but the key operational traits an agent needs are present.

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?

Purpose and the primary when-to-use condition are front-loaded in the first sentence, with cost and diagnostic contents following. The prose is dense but nearly every clause carries new information; the only mild redundancy is describing output rows when an output schema exists.

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?

With zero params, full annotations, and an output schema already supplied, the description only needs to cover positioning and any non-structural behavior. It does both: when to run it, what it costs, what it reveals, and what to do with the version signal.

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 no parameter semantics to compensate for; baseline 4 applies. The description does not waste space restating an empty schema, which is appropriate.

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 a concrete verb and resource ("Check the Claude Code setup") and scopes it with "for hosts other than Claude Code," then enumerates what it inspects: bridge version, claude version, auth state, session location. It never names a sibling *_status tool to contrast with, so differentiation from claude_ask/claude_continue or codex_status rests on the host-scope clause rather than an explicit comparison.

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?

It gives a concrete trigger ("run it first when a call says 'not found'"), a cost rationale ("Spends no quota"), and a follow-up action ("if so, tell the user"). The "for hosts other than Claude Code" clause implies an exclusion, but no named alternative tool is offered for the Claude Code case, leaving that routing to inference.

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