VibeRaven

Search VibeRaven launch guides

search_guides

Read-onlyIdempotent

search_guides({"query":"supabase tables missing rls"}) Find troubleshooting steps for exact errors in Supabase RLS, Realtime and auth; Clerk middleware and sessions; Better Auth origins and OAuth callbacks; Vercel environment variables and deployments; Stripe webhooks; or Storybook environment variables and 404s. Search published viberaven.dev guides by keywords or error text; returns up to 5 titles, URLs and short answers. Also covers Lovable + Supabase launch checks and client handoff. No match returns an empty list. Limits: searches the indexed published guides only; does not browse the web or read your project.

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": {
      "query": "<query>"
    },
    "name": "search_guides"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	A few keywords or the exact error text, for example "supabase tables missing rls". Long text is searched by its first 200 characters.

Output Schema

Name	Required	Description	Default
`results`	Yes
`nextStep`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026
- addedOutput schema / properties / nextStep / properties / codingAgentTask
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedOct 31, 2026

changedInput schema / properties / query / description

Previous value: -"A few keywords from the question, for example \"supabase tables missing rls\"."New value: +"A few keywords or the exact error text, for example \"supabase tables missing rls\". Long text is searched by its first 200 characters."

changedInput schema / properties / query / maxLength
```
Previous value: -200New value: +4000
```

Changed1 schema field changedOct 31, 2026

addedOutput schema / properties / nextStep

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "label": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "label",
+    "url"
+  ],
+  "type": "object"
+}

First observedOct 1, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description wisely spends its space on what annotations can't say: it searches only indexed published guides and returns at most 5 results. The empty-list-on-no-match note is useful but partly redundant with the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Mostly front-loaded and information-dense, but opening with a raw JSON call snippet ('search_guides({"query":...})') is wasted space that duplicates the schema, and the long semicolon-separated domain list reads as a run-on.

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 single-parameter search tool with an output schema, this covers scope, result cardinality, no-match behavior, and hard limits. Nothing an agent needs in order to call it correctly is missing.

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% and the parameter description already explains keywords, exact error text, and the 200-character truncation. The description's query example duplicates what the schema shows, so it adds little beyond the structured field.

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 specific verb and resource ('Search published viberaven.dev guides by keywords or error text') and enumerates the concrete error domains covered (Supabase RLS, Clerk middleware, Stripe webhooks, etc.), which clearly separates it from siblings like check_supabase_migrations or provider_playbook.

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?

Tells the agent to use it for 'troubleshooting steps for exact errors' and includes explicit exclusions ('does not browse the web or read your project'). It stops short of naming a sibling tool as the alternative for live project inspection, but the negative scope is clear enough to route correctly.

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

All VibeRaven 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.