Skip to main content
Glama
Sign In
kimi-code-mcp

kimi-code-mcp

by oni-chan69
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kimi_cache_status

View session cache statistics including hits, misses, active sessions, and performance metrics to monitor cache effectiveness and troubleshoot issues.

Instructions

View session cache statistics and status. Shows cache hits/misses, active sessions, and performance metrics. Use this to monitor cache effectiveness and troubleshoot issues.

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_cache_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNoShow detailed cache entry information (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility. It implies a read-only operation ('View'), but does not disclose potential side effects, permission requirements, or rate limits. Minimal behavioral insight beyond the basic purpose.

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?

Two concise sentences: first states purpose, second adds usage guidance and output summary. No wasted words, though slightly more detail on output could be added without harming conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a single parameter, no output schema, and no annotations, the description adequately covers purpose and usage. However, it lacks details on return format, pagination, or performance overhead, leaving some gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with one boolean parameter 'detail' already described in the schema. The description adds no extra meaning beyond the schema, so baseline score applies.

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?

Description explicitly states 'View session cache statistics and status,' specifying the verb and resource. It distinguishes itself from sibling tools like kimi_cache_invalidate (mutation) implicitly, but does not strongly differentiate from kimi_status, which might also show status.

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?

The description advises using the tool 'to monitor cache effectiveness and troubleshoot issues,' providing context. However, it does not explicitly state when not to use it or mention alternatives, leaving some guidance implicit.

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

Deploy Server

Other Tools