Skip to main content
Glama

Query Vibe proxy

query_vibe_proxy

Send a query to the Vibe CLI proxy and return its JSON response or an error if the proxy is unavailable.

Instructions

Send a query to the Vibe CLI proxy. Use get_vibe_proxy_status first if you only need liveness. Local HTTP POST. Returns the proxy JSON or an error when the proxy is down.

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": "query_vibe_proxy"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesQuery text to send to the Vibe proxy. Non-empty string.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv6.2.1
    • addedInput schema / properties / query / description
      Added value: +"Query text to send to the Vibe proxy. Non-empty string."
  2. First observedv5.0.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is largely covered. The description adds real value by disclosing the transport ('Local HTTP POST') and failure behavior ('returns an error when the proxy is down'). However, it never addresses side effects, cost/latency, or whether a non-idempotent open-world POST can change remote state — the biggest gap for a write-flagged call into an external CLI.

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?

Three short sentences, front-loaded with the core action, then the sibling routing rule, then transport and failure semantics. No filler, no repetition of the title. It could be marginally tighter but every sentence earns its place.

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?

An output schema exists, so return values need not be explained, and the description still notes the error case. But 'Vibe CLI proxy' is unexplained domain jargon, and with 40+ siblings the agent gets no sense of what kinds of queries belong here versus query_local_ai_service, chat_with_model, or ask_frontier. Adequate but with a clear differentiation gap.

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 description coverage is 100% with a single documented parameter ('Query text to send to the Vibe proxy. Non-empty string.'), so the schema carries full weight and baseline is 3. The description adds no syntax, format, or length guidance about what a valid query looks like beyond restating the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb (send a query) and a specific resource (the Vibe CLI proxy), so the action is unambiguous. It also distinguishes itself from the sibling get_vibe_proxy_status by scope, though it does not distinguish itself from other query-style siblings like query_local_ai_service or query_nexus.

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?

It explicitly names an alternative tool and the condition that selects it: "Use get_vibe_proxy_status first if you only need liveness." That is a concrete routing rule. It stops short of saying when this tool should be chosen over the many other query/chat siblings, and gives no prerequisites.

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