VibeKit

VibeKit Database Schema

vibekit_db_schema

Read-onlyIdempotent

Get an app's database schema — every table and its columns. Always call this before writing a query with vibekit_db_query.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "appId": "<appId>"
    },
    "name": "vibekit_db_schema"
  }
}

Input Schema

Name	Required	Description	Default
`appId`	Yes	App ID (from vibekit_list_apps)

Output Schema

Name	Required	Description
`ok`	Yes	Whether the call succeeded.
`data`	No	Full database schema: tables, columns, and types.
`error`	No	Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Result envelope: ok=true with data on success, ok=false with error on failure.",
+  "properties": {
+    "data": {
+      "description": "Full database schema: tables, columns, and types."
+    },
+    "error": {
+      "description": "Error message when ok is false (e.g. missing/invalid VIBEKIT_API_KEY, or an API error).",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the call succeeded.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

First observedJul 15, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already provide readOnlyHint and idempotentHint. Description adds that it returns full schema and is a prerequisite, but no further behavioral details needed beyond annotations.

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?

Two efficient sentences: first states purpose, second provides critical usage guidance. No redundant words.

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?

Fully adequate given 1 parameter, high schema coverage, output schema presence, and annotations. Covers purpose, prerequisite, and scope.

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% for the single parameter 'appId', with description referencing vibekit_list_apps. Description adds no extra semantic 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 retrieves database schema (tables and columns). Uses specific verb 'Get' and resource 'database schema'. Distinct from siblings like vibekit_db_query.

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 to call this before vibekit_db_query. However, does not mention alternatives like vibekit_db_table for single table schema.

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

All VibeKit tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.