Skip to main content
Glama

Muse bridge diagnostics

muse_status
Read-onlyIdempotent

Check Muse Code setup without spending quota: verifies the binary, credentials, model catalog, sandbox state, and bridge version for available updates. Run it first when a call returns "not found".

Instructions

Check the Muse Code 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 which muse binary runs, whether credentials exist (not whether they are valid: Muse has no free auth probe), the model catalog, the Windows sandbox state, and where muse keeps its data.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.32.1

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavioral limits: it spends no quota, checks credential existence but not validity because there is no free auth probe, and indicates when a newer agent-intern release is available. These details materially help the agent interpret and act on the results.

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 purpose is front-loaded, followed immediately by cost, usage trigger, and the specific diagnostics returned. Every sentence contributes useful information without filler.

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?

Given zero parameters, an output schema, and strong annotations, the description is complete. It explains what the diagnostic covers, its limits, and how to use the bridge version information.

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 no parameters, so there is no parameter meaning to add. The baseline for zero-parameter tools applies.

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 states a specific verb and resource: checking the Muse Code setup. It also enumerates exactly what the diagnostic covers, including the binary, credentials, model catalog, sandbox state, and data location, which clearly distinguishes it from Muse ask/continue tools.

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 clear trigger to run this first when a call reports "not found" and notes that it spends no quota. It does not state explicit when-not conditions or name alternative diagnostics, but the primary usage context is clear.

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