Skip to main content
Glama

Vibe Springs

by net.vibesprings

check_watch

Check a watch condition by ID. Evaluates if the condition has been met relative to the caller's previous baseline, updates baseline to current, and sends notifications if triggered. [PAID: $0.008 USDC per call via x402 on Base. First call without payment_signature returns the payment requirements.]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe watchId 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.1/5.0
Behavior4/5

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

Discloses side effects (updates baseline, sends notifications) and payment mechanism (x402 on Base). No annotations exist, so description carries full burden; covers key behaviors well.

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 sentences plus a payment note in brackets, front-loaded with core purpose, no wasted words. Concise and well-structured.

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?

No output schema, so description should mention return value. It does not specify what the tool returns (e.g., status, success/failure). Covers behavior but missing output details for completeness.

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% (both parameters described). Description adds value for payment_signature by explaining the two-step flow and token acquisition, beyond schema details.

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?

Clearly states the verb (check), resource (watch condition by ID), and actions (evaluates condition, updates baseline, sends notifications). Distinguishes from sibling 'check_watches_batch' implicitly by being for a single ID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides payment flow guidance (first call without payment_signature) but lacks explicit when-to-use vs alternatives like check_watches_batch or other sibling tools. Adequate but could be improved.

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