Skip to main content
Glama

Vibe Springs

by net.vibesprings

check_watches_batch

Batch check up to 5 watch conditions concurrently. If individual watches fail or are missing, error objects are returned inline to prevent batch interruption. [PAID: $0.02 USDC per call via x402 on Base. First call without payment_signature returns the payment requirements.]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesComma-separated watch IDs to check
payment_signatureNoOptional x402 payment token. Call the tool WITHOUT this first to receive payment requirements (price, payTo, asset, nonce rules), sign the exact-scheme EIP-712 USDC authorization with your wallet, then retry with this field set to the base64 token.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are provided, so the description carries full burden. It discloses the paid nature ($0.02 USDC via x402), the payment flow, error handling with inline error objects, and the batch behavior. This is comprehensive and honest.

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?

Two clear sentences plus a bracketed payment note. First sentence states purpose and key detail. Every word earns its place, no redundancy.

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?

The description covers purpose, constraints, error handling, and payment. However, with no output schema, it does not describe the success response format. The explanation is otherwise sufficient for an AI to use the tool correctly.

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?

Schema coverage is 100%, so baseline is 3. The description adds the constraint of up to 5 IDs (not in schema) and summarizes the payment flow for 'payment_signature'. This extra context improves parameter understanding.

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 'check' and resource 'watch conditions' in batch mode, up to 5 concurrently. It distinguishes itself from the sibling tool 'check_watch' by specifying batch capability. The purpose is specific and unambiguous.

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 provides clear usage context: batch checking up to 5 watches, how to handle payment (call without signature first), and error behavior. It does not explicitly mention when to use alternatives like 'check_watch', but the batch nature implies when to prefer this tool.

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

All Vibe Springs toolsInspect
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

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes, but get_crypto_prices overlaps partially with get_market_pulse (which includes crypto prices), and get_exchange_rates overlaps with convert_currency. Descriptions clarify boundaries, but minor confusion possible.

Naming Consistency4/5

Nearly all tools follow a get_<noun> or verb_noun pattern, with consistent snake_case. The only outlier is 'health' which is a single word, but it still fits as a status endpoint.

Tool Count4/5

22 tools is slightly high for a single server, but each tool offers a distinct paid endpoint and the variety justifies the count. The server would benefit from a bit more focus, but it's still acceptable.

Completeness4/5

The server covers a wide range of data (crypto, weather, finance, on-chain risk, travel) with search and health endpoints. Missing operations like delete_watch or list_watches are minor gaps, but core functionality is well represented.

Resources