Skip to main content
Glama

Kimi bridge diagnostics

kimi_status
Read-onlyIdempotent

Checks Kimi Code setup without using quota, verifies bridge and Kimi versions, provider configuration, and data location; run first when a call reports 'not found'.

Instructions

Check the Kimi 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 kimi's version, whether a provider is configured (kimi provider list; expect "no providers configured" until you log in), and where Kimi 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": "kimi_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, and the description adds genuinely non-obvious behavior: it spends no quota, and it sets expectations for output ("expect 'no providers configured' until you log in"), which prepares the agent for a normal-looking non-error state. It does not cover failure modes of the diagnostic itself, keeping it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and every sentence carries information (cost, trigger, expected outputs). It is dense with parentheticals and backticked command names, making it slightly crowded, but nothing is truly redundant.

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?

An output schema exists, so the description need not explain return values, yet it usefully flags the two rows an agent should act on. For a zero-parameter read-only diagnostic, this is essentially complete; only the absence of failure/error semantics leaves a small gap.

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, which is the baseline-4 case. The backticked `kimi provider list` reference describes internal mechanics rather than parameters, so it neither helps nor hurts parameter understanding.

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 concrete verb and resource ("Check the Kimi Code setup") and enumerates what is inspected: bridge version, kimi version, provider configuration, data location. An agent can distinguish it from the ask/continue siblings, though it does not explicitly name those as the alternatives it is not.

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 condition — "run it first when a call says 'not found'" — plus a diagnostic follow-up ("if so, tell the user" about a newer release). Missing an explicit negative case (e.g., when not to bother running diagnostics), but the context is clear enough to act on.

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