VibeKit

VibeKit Browse Table

vibekit_db_table

Read-onlyIdempotent

Browse rows of one table with pagination and optional sorting — a quick read-only alternative to hand-writing a SELECT.

Input Schema

TableJSON Schema

Name	Required	Description
`appId`	Yes	App ID (from vibekit_list_apps)
`limit`	No	Max rows to return (default 50, max 200)
`table`	Yes	Table name (see vibekit_db_schema)
`offset`	No	Row offset for pagination (default 0)

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	Whether the call succeeded.
`data`	No	Rows from the requested table with pagination applied.
`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. Dates show when Glama detected each change.

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": "Rows from the requested table with pagination applied."
+    },
+    "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/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description reinforces these with 'read-only' and adds pagination/sorting context, providing additional behavioral insight 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?

One sentence, front-loaded with the tool's purpose, and no redundant information. Every part is essential.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists, return values need not be explained. However, the mention of sorting without a corresponding parameter leaves an incomplete picture. Adequate but with a notable gap.

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

Parameters2/5

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

Schema coverage is 100%, baseline 3. However, the description mentions 'optional sorting' but no sort parameter exists in the schema, introducing a discrepancy that could mislead an agent. This negative impact lowers the score.

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 clearly states the verb 'browse', the resource 'rows of one table', and includes pagination and optional sorting. It distinguishes itself from siblings like vibekit_db_query by calling it a 'quick read-only alternative to hand-writing a SELECT'.

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 implies when to use (quick read-only browse) and contrasts with writing a SELECT, but does not explicitly mention alternatives or when not to use. Slightly lacking in exclusion guidance.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Most tools have distinct purposes, but vibekit_chat and vibekit_submit_task both handle AI-driven code changes, leading to potential confusion. Descriptions help differentiate, but overlap exists.

Naming Consistency4/5

All tools use the 'vibekit_' prefix and lowercase with underscores. Most follow a verb_noun pattern, but a few (e.g., 'vibekit_account') are noun-only, causing minor inconsistency.

Tool Count3/5

36 tools is on the high side, covering many aspects of the platform. While mostly justified, the count feels slightly excessive and could be streamlined.

Completeness5/5

The tool set covers the full lifecycle of apps, databases, tasks, schedules, skills, QA, and environment variables. No obvious gaps for the stated domain.

VibeKit Browse Table

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources