moonbridge

Overview Schema Source Related Servers Discussions Admin

List server capabilities (free)

kimi_capabilities

Read-only

List server tools, tiers, and result fingerprint; choose detail levels or embed schemas to verify capabilities and cache responses for clients without resource access.

Instructions

List this server's tools, tiers, and the result fingerprint. Free — no model call. Clients can cache by the fingerprint.

detail="summary" (default) returns each tool's name, cost, stability, and error_codes — the facts tools/list does not already carry — plus async_lifecycle, but only for the *_async tools. detail="full" adds use_when/returns/required_params/key_optional_params, restating what you already hold. detail="contracts" omits tool_details.

Pass include_schemas to also embed the full 'error-envelope', 'result-meta', 'capabilities-result', and/or 'status-result' schema, and/or the 'parameter-contracts' document (a contract doc, not a JSON Schema) — a tool-reachable fallback to the kimi:// resources for resource-blind clients. It works in any detail mode.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`detail`	No	What to return: 'summary' (default) returns each tool's name, cost, stability, and error_codes; the *_async tools also get async_lifecycle. 'full' adds use_when, returns, and the parameter lists (which tools/list already carries). 'contracts' drops tool_details: fetch a schema, or recheck fingerprint, without re-paying for the inventory.	summary
`include_schemas`	No	Opt-in tool-reachable fallback for resource-blind clients: also embed the full 'error-envelope', 'result-meta', 'capabilities-result', and/or 'status-result' schema, and/or the 'parameter-contracts' document (a contract doc, not a JSON Schema, sourced from the kimi://params resource body), in the response — the default payload omits them and points at the kimi:// resources instead.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Sep 2, 2026

changedOutput schema / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "active_tools": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "annotations_reading": {
-        "type": "string"
-      },
-      "deprecation_policy": {
-        "type": "string"
-      },
-      "error_envelope_resource": {
-        "type": "string"
-      },
-      "fingerprint": {
-        "type": "string"
-      },
-      "fingerprint_covers": {
-        "description": "A contract-semantic change in any listed category changes the fingerprint; nothing outside them does. Release identity is excluded: serverInfo.version, version, server_version change every release WITHOUT moving the fingerprint.",
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "free_tools": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "name": {
-        "type": "string"
-      },
-      "negative_scope": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "ok": {
-        "const": true,
-        "type": "boolean"
-      },
-      "prerequisites": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "protocol_revision": {
-        "type": "string"
-      },
-      "resource_error_carrier": {
-        "type": "string"
-      },
-      "result_meta_resource": {
-        "type": "string"
-      },
-      "sandboxes": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "schemas": {
-        "anyOf": [
-          {
-            "additionalProperties": true,
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "scope": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "server_version": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "stability": {
-        "type": "string"
-      },
-      "tiers": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "tool_details": {
-        "description": "Per-tool capability records; full schema at resource kimi://capabilities-result",
-        "type": "array"
-      },
-      "tool_error_carrier": {
-        "type": "string"
-      },
-      "transport": {
-        "type": "string"
-      },
-      "version": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "name",
-      "version",
-      "transport",
-      "stability",
-      "active_tools",
-      "free_tools",
-      "tiers",
-      "sandboxes",
-      "scope",
-      "negative_scope",
-      "prerequisites",
-      "deprecation_policy"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "error": {
-        "description": "Populated error envelope; full schema at resource kimi://error-envelope",
-        "type": "object"
-      },
-      "meta": {
-        "type": "object"
-      },
-      "ok": {
-        "const": false
-      }
-    },
-    "required": [
-      "ok",
-      "error",
-      "meta"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "active_tools": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "annotations_reading": {
+        "type": "string"
+      },
+      "deprecation_policy": {
+        "type": "string"
+      },
+      "error_envelope_resource": {
+        "type": "string"
+      },
+      "fingerprint": {
+        "type": "string"
+      },
+      "fingerprint_covers": {
+        "description": "A contract-semantic change in any listed category changes the fingerprint; nothing outside them does. Release identity is excluded: serverInfo.version, version, server_version change every release WITHOUT moving the fingerprint.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "free_tools": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "name": {
+        "type": "string"
+      },
+      "negative_scope": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "ok": {
+        "const": true,
+        "type": "boolean"
+      },
+      "prerequisites": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "protocol_eras_served": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "protocol_revision": {
+        "type": "string"
+      },
+      "resource_error_carrier": {
+        "type": "string"
+      },
+      "result_meta_resource": {
+        "type": "string"
+      },
+      "sandboxes": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "schemas": {
+        "anyOf": [
+          {
+            "additionalProperties": true,
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "scope": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "server_version": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "stability": {
+        "type": "string"
+      },
+      "tiers": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "tool_details": {
+        "description": "Per-tool capability records; full schema at resource kimi://capabilities-result",
+        "type": "array"
+      },
+      "tool_error_carrier": {
+        "type": "string"
+      },
+      "transport": {
+        "type": "string"
+      },
+      "version": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "version",
+      "transport",
+      "stability",
+      "active_tools",
+      "free_tools",
+      "tiers",
+      "sandboxes",
+      "scope",
+      "negative_scope",
+      "prerequisites",
+      "deprecation_policy"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "error": {
+        "description": "Populated error envelope; full schema at resource kimi://error-envelope",
+        "type": "object"
+      },
+      "meta": {
+        "type": "object"
+      },
+      "ok": {
+        "const": false
+      }
+    },
+    "required": [
+      "ok",
+      "error",
+      "meta"
+    ],
+    "type": "object"
+  }
+]

First observedv0.1.0Aug 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that no model call is made, that responses are cacheable via fingerprint, and that certain detail modes restate data the client already has. It also explains the fallback behavior for resource-blind clients and clarifies that parameter-contracts is a contract document, not a JSON Schema.

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 front-loaded with the core purpose, cost, and caching behavior. The detail-mode explanations are dense and information-rich, with each sentence adding a distinct fact. It could be tightened slightly, but the structure makes the complexity navigable.

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?

Given the output schema exists and annotations cover read-only safety, the description provides everything an agent needs to call this tool correctly: purpose, cost model, caching, detail-level tradeoffs, include_schemas behavior, and fallback rationale. No significant gap remains.

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 100%, so the schema already documents both parameters. The description adds meaningful nuance beyond the schema: which tools get async_lifecycle, that 'full' restates existing data, and that include_schemas is an opt-in fallback sourced from kimi:// resources. This helps an agent reason about payload tradeoffs.

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 opens with a specific verb and resource: 'List this server's tools, tiers, and the result fingerprint.' It clearly distinguishes this from the sibling tools by emphasizing that it is free, caching-friendly, and returns capability metadata rather than status, models, or job operations.

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?

The description gives strong usage context: it is free, makes no model call, and is designed for clients to cache by fingerprint. It also explains when to use different detail modes and when to pass include_schemas, though it does not explicitly name sibling tools as alternatives or provide when-not-to-use conditions.

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

Deploy Server