Loading ToolBench
OVB3 (Oracle Visual Builder Bridge) — MCP server + CLI + Claude Code plugin for driving Oracle Visual Builder Studio (VBS) git-backed app development from Claude: read/write VBCS artifacts, run Oracle's build/audit tasks, and git commit/push/pull.
Server has 19 tools with explicit Zod schemas and descriptions. Naming follows verb_noun convention (list_, read_, write_, git_, run_, vbcs_, vbstudio_). Most tools have 50-150 char descriptions meeting baseline (p10=34, p90=392). However, 3 tools are marked [NOT IMPLEMENTED], reducing effective coverage. Parameter descriptions are present but often generic (e.g., 'Repo checkout to target' repeated 16 times verbatim). Output schemas are not documented, responses are JSON-stringified but structure is opaque to LLMs. Error handling wraps exceptions into isError responses but provides no recovery guidance or categorization. No tool annotations (readOnlyHint/destructiveHint) despite clear risk levels. Missing: pagination for list tools, per-item success/failure for batch operations, and natural-language identifiers (tools require absolute paths or repo names, not user-friendly shortcuts).
Clone a git remote into VBS_WORKSPACE_DIR so it's discoverable by list_repos. Used by /link's VBS setup flow.
Stage and commit changes in a repo checkout.
Pull from the repo's remote.
Push to the repo's remote.
Show git status for a repo checkout.
List VBCS web app names (webApps/<name>) present in a repo checkout.
List artifact files in a repo matching a glob pattern, e.g. 'webApps/*/flows/**/*.json'.
Three tools marked [NOT IMPLEMENTED] reduce effective coverage and confuse LLMs about availability. vbstudio_list_projects, vbstudio_trigger_build, vbstudio_trigger_deploy should either be removed or have descriptions stating 'Blocked: awaiting live dev instance' with clear next steps.
Output schemas are not documented. Tools return JSON-stringified results but LLMs cannot see field names, types, or structure. E.g., list_repos returns what? Array of strings? Objects with name/path? This forces LLMs to guess and parse unstructured output.
Repo parameter description repeated verbatim 16 times. Generic descriptions like 'Repo checkout to target' do not explain WHEN to use absolute path vs repo name vs omit. LLMs cannot infer the resolution logic from the description alone.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | <=2025-11-25 | v2 |
List local VB Studio project repo checkouts discoverable under VBS_WORKSPACE_DIR.
Read a VBCS artifact file (page/flow/chain/service JSON, etc) by repo-relative path.
Run grunt-vb-audit for a VBCS app. Streams output live to server logs as it runs.
Run grunt-vb-build for a VBCS app. Streams output live to server logs as it runs.
Export a business object's data records from a standalone VBCS instance.
List applications on a standalone VBCS instance via its REST API (VBCS_BASE_URL). For VBCS apps not backed by a VB Studio git repo.
Lock a live application on a standalone VBCS instance.
Unlock a live application on a standalone VBCS instance.
[NOT IMPLEMENTED] List VB Studio projects on the instance. Blocked until a live dev instance is confirmed.
[NOT IMPLEMENTED] Trigger a CI/CD build via the VB Studio REST API. Blocked until a live dev instance is confirmed.
[NOT IMPLEMENTED] Trigger a deploy via the VB Studio REST API. Blocked until a live dev instance is confirmed.
Write a VBCS artifact file by repo-relative path. Refuses invalid JSON for .json paths.
No tool annotations (readOnlyHint/destructiveHint/idempotentHint) despite clear risk levels. write_artifact, git_commit, git_push, git_clone, vbcs_lock_application, vbcs_unlock_application are destructive but unmarked. Agents cannot distinguish safe from risky operations.
Error handling returns isError=true with raw exception messages (e.g., 'ENOENT: no such file or directory'). No recovery guidance, categorization (retryable vs user-fixable), or actionable next steps. LLMs cannot self-correct from these errors.