Skip to main content
Glama
ryanameier

kimi-swarm-bridge

by ryanameier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Find Recent Kimi Session

kimi_find_recent_session
Read-onlyIdempotent

Search recent Kimi sessions by title, status, or working directory to recover interrupted work or dedupe sessions when the exact ID is unknown. Read-only results include next-step guidance.

Instructions

Find recent Kimi sessions whose titles contain a requested substring, optionally constrained by status and working directory. Use for interruption recovery or dedupe when the exact session ID is unknown; prefer session-ID-based tools once a match is known. This is read-only and returns matching candidates plus status-aware next-step guidance without creating or modifying a session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNoOptional working directory used to constrain matches to the same workspace. Recommended for safe recovery/dedupe.
statusNoOptional exact Kimi session-status filter, such as running, idle, awaiting_approval, awaiting_question, aborted, or failed.
pageSizeNoMaximum number of recent sessions to inspect. Defaults to 20.
matchAnyCwdNoSet true only when intentionally allowing a title match from any working directory. Defaults to false when cwd is provided.
excludeEmptyNoWhether sessions with no messages should be excluded from the search.
titleContainsYesCase-insensitive substring that must appear in the Kimi session title. Leading and trailing whitespace is ignored.
includeArchiveNoWhether archived Kimi sessions should be included in the search.
includeSummaryNoFetch message count and latest meaningful user/assistant messages for candidates. Adds latency; leave false unless recovery context is needed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.3.2
    • addedInput schema / properties / cwd / description
      Added value: +"Optional working directory used to constrain matches to the same workspace. Recommended for safe recovery/dedupe."
    • addedInput schema / properties / excludeEmpty / description
      Added value: +"Whether sessions with no messages should be excluded from the search."
    • addedInput schema / properties / includeArchive / description
      Added value: +"Whether archived Kimi sessions should be included in the search."
    • addedInput schema / properties / includeSummary / description
      Added value: +"Fetch message count and latest meaningful user/assistant messages for candidates. Adds latency; leave false unless recovery context is needed."
    • addedInput schema / properties / matchAnyCwd / description
      Added value: +"Set true only when intentionally allowing a title match from any working directory. Defaults to false when cwd is provided."
    • addedInput schema / properties / pageSize / description
      Added value: +"Maximum number of recent sessions to inspect. Defaults to 20."
    • addedInput schema / properties / status / description
      Added value: +"Optional exact Kimi session-status filter, such as running, idle, awaiting_approval, awaiting_question, aborted, or failed."
    • addedInput schema / properties / titleContains / description
      Added value: +"Case-insensitive substring that must appear in the Kimi session title. Leading and trailing whitespace is ignored."
  2. First observedv0.3.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description reinforces this and adds extra context: it returns 'matching candidates plus status-aware next-step guidance' and warns about latency for includeSummary. It discloses behavior beyond annotations without contradiction.

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 description is three sentences, front-loaded with purpose, and each sentence adds value: function, usage context with alternative, and read-only output behavior. 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?

For a search/find tool with fully documented parameters and safety annotations, the description covers purpose, usage, and output nature. It mentions status-aware next-step guidance and latency trade-offs, though it doesn't detail the exact return structure. Given no output schema exists, this is nearly complete.

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 detailed descriptions for all 8 parameters. The description does not add parameter-specific semantics beyond what the schema already provides; it only generalizes about status and working directory filters. Baseline 3 is appropriate given full schema coverage.

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 explicitly states the tool finds recent Kimi sessions by title substring, with optional filters on status and working directory. It also names the exact use case (interruption recovery/dedupe when session ID is unknown) and contrasts with session-ID-based tools, clearly distinguishing it from siblings like kimi_recent_sessions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance: 'Use for interruption recovery or dedupe when the exact session ID is unknown; prefer session-ID-based tools once a match is known.' This clearly routes the agent to alternatives once a match is found, leaving no ambiguity.

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