Skip to main content
Glama

digest-kimi

Read-only

Ingest multiple files or directories to answer a focused question using extended context. Walks directories, filters files, and returns a concise answer.

Instructions

Ingest many files at once and answer a focused question. Uses Kimi's 262K context to swallow whole modules / docs that don't fit in the caller's context. Walks directories, filters by extension, truncates oversized files, caps total payload. Returns a concentrated brief.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelNo
pathsYesFiles or directories to ingest. Directories are walked. Globs are NOT expanded — pass concrete paths.
shapeNosummary: 1-paragraph; detailed: structured deep-dive; qa: focused answer to the question.qa
excludeNoSubstrings to exclude from paths (matched against relative path). Default: node_modules, .git, dist, build.
timeoutNo
questionYesFocused question to answer using the provided files (e.g., "explain auth flow", "find dead code").
recursiveNoWalk into subdirectories. Default: true.
extensionsNoFilter by extensions when walking dirs (e.g., [".ts", ".tsx"]). Default: all text-like files.
workingDirNo
maxTotalBytesNoStop adding files once the total payload exceeds this (Kimi context is ~262K tokens / ~1MB safe). Default: 8 MB.
maxBytesPerFileNoTruncate any single file above this size. Default: 200 KB.
Behavior4/5

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

Annotations declare readOnlyHint=true, destructiveHint=false. Description adds: walks directories, filters by extension, truncates oversized files, caps total payload. No contradictions.

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?

Three sentences, front-loaded with purpose, clear and efficient. No wasted words.

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?

Covers purpose, key behaviors, and constraints. Could be more specific about output format, but given no output schema, 'concentrated brief' is sufficient.

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?

Schema coverage is 73%. Description adds context by mentioning directory walking, extension filtering, truncation, and payload capping, which correspond to parameters. Adds value beyond schema.

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?

Clearly states it ingests many files and answers a focused question using Kimi's large context. Distinguishes from siblings like 'ask-kimi' by emphasizing bulk ingestion and focused answering.

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?

Explicitly says when to use: when files don't fit in the caller's context. Does not provide when-not or alternatives, but context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/x51xxx/kimi-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server