Skip to main content
Glama

Get Vibe proxy status

get_vibe_proxy_status
Read-onlyIdempotent

Checks whether the Vibe CLI proxy port is up and returns JSON status, so you can confirm the proxy is available before sending queries.

Instructions

Check whether the Vibe CLI proxy port is up. Use query_vibe_proxy to send a query. Local HTTP. Returns JSON status or unavailable.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_vibe_proxy_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv5.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld. The description adds useful channel context ('Local HTTP') and notes the outcome may be 'unavailable', which signals a failure mode beyond the annotations.

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?

Four short sentences, front-loaded with the core purpose and no wasted prose. The 'Returns JSON status or unavailable' clause is slightly redundant against the existing output schema.

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

Completeness4/5

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

With full annotation coverage, an output schema and no parameters, the description supplies everything needed to decide when to call it. Only a note on auth or failure handling keeps it short of complete.

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

Parameters4/5

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

Zero parameters, so the baseline is 4. There is nothing about inputs an agent could get wrong.

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?

States a specific verb and resource: checking whether the Vibe CLI proxy port is up. It distinguishes itself from the sibling that actually sends queries. It is slightly less precise about how it differs from the generic get_status sibling.

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 names query_vibe_proxy as the follow-up tool for sending a query, implying this is the pre-flight check. It gives clear context but doesn't state exclusions or prerequisites for when not to use it.

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