Skip to main content
Glama
ryanameier

kimi-swarm-bridge

by ryanameier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Kimi Swarm Settings

kimi_swarm_settings
Idempotent

Set or read the worker limit Kimi may use per task and update the offerKimi preference. Call without arguments to view current settings; supply maxAgents or offerKimi to change them.

Instructions

Show or change how many AgentSwarm workers Kimi may use per task. maxAgents is a ceiling: Kimi still decides how many workers each task needs and uses fewer for small tasks. Call with maxAgents when the user asks to raise or lower the agent limit (for example "increase the limit to 20"); call with no arguments to report the current settings. Values above the deployment cap are reduced to the cap. The response also reports concurrency, the number of workers that run at the same time (set by the deployment admin); extra workers queue, which keeps simultaneous ai& requests bounded, and Kimi backs off automatically if ai& rate-limits. offerKimi is the user's preference for Kimi taking independent parts of requests they did not send to Kimi: ask (default: offer and wait for a yes), auto (hand them over and say so) or off (only when the user asks for Kimi); read it before your first offer in a conversation, and save it when the user says to always do it or to stop asking.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxAgentsNoNew ceiling on workers per task. Omit to only read the current settings.
offerKimiNoNew preference for offering Kimi on parts of requests: ask, auto or off. Omit to keep it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.1
    • addedInput schema / properties / offerKimi
      Added value: +{
+  "description": "New preference for offering Kimi on parts of requests: ask, auto or off. Omit to keep it.",
+  "enum": [
+    "ask",
+    "auto",
+    "off"
+  ],
+  "type": "string"
+}
  2. Addedv0.4.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations provide idempotentHint and destructiveHint, but the description goes far beyond by explaining that maxAgents is a ceiling (not a hard number), that values above deployment cap are reduced, concurrency behavior, queueing, rate-limit backoff, and offerKimi semantics. No contradiction with annotations; description adds rich behavioral context.

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?

The description is long but dense; every sentence adds necessary detail. It front-loads the main purpose and then elaborates. It could be slightly tighter, but the complexity justifies the length. Not overly verbose.

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?

For a tool with two optional parameters and no output schema, the description explains what the response reports (concurrency, queueing, backoff) and how to use it. All needed information for correct invocation is present.

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

Parameters5/5

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

Schema coverage is 100%, so baseline is 3, but description adds substantial meaning: explains maxAgents is a ceiling, how it gets reduced, offerKimi values (ask/auto/off) with default and behavior. This goes well beyond the schema's descriptions.

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?

States a clear verb ('Show or change') with a specific resource (AgentSwarm workers per task). It distinguishes itself from sibling tools like kimi_model_settings by specifying the exact resource. An agent can immediately understand what this tool does.

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?

Explicitly describes when to call with maxAgents (when user asks to raise/lower limit) and when to call with no arguments (to report current settings). Also gives guidance on offerKimi usage ('read it before your first offer', 'save it when the user says...'). This is excellent usage guidance.

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