Skip to main content
Glama

Vibes-Coded Agent Security and Commerce Tools

by io.github.doteyeso-ops

vc_web_search

Read-onlyIdempotent

Run a public web search and return titles, URLs, and snippets as JSON.

Use when you need current public web results for a query.
Do not use for private/intranet pages — call vc_page_markdown with a known URL instead.
Sibling: vc_page_markdown (one URL), pay (generic slug caller).

Auth: free-trial or prepaid X-Vibes-Key preferred; else USDC via x402 (~$0.02).
Side effects: outbound HTTP to a search provider; no local writes.
Returns JSON results, or a payment_required challenge if unpaid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query string.
max_resultsNoMax results to return (typical 1–10).
payment_signatureNoOptional x402 PAYMENT-SIGNATURE if not using X-Vibes-Key.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

TDQS

A4.7/5.0
Behavior5/5

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

Even with readOnly/openWorld/idempotent annotations already present, the description adds meaningful behavior: auth/payment requirements (X-Vibes-Key vs x402 USDC), an outbound HTTP side effect, no local writes, and a possible 'payment_required' challenge response. No claim contradicts 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.

Conciseness5/5

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

The description is compact and front-loaded: core behavior first, then usage boundaries, then auth/side effects. Each line carries distinct information, and the sibling note is a single clarifying clause rather than a duplicate explanation.

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?

With an output schema present and all parameters documented, the description supplies the missing context: when to choose this tool, how to authenticate/pay, and what failure/payment signals to expect. Nothing an agent needs 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 description coverage is 100%, so the schema documents query, max_results, and payment_signature. The description gives auth context and output shape but adds no per-parameter meaning beyond the schema; the high-coverage baseline of 3 applies.

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?

Opens with a specific verb and resource — 'Run a public web search' — and states the exact return payload ('titles, URLs, and snippets as JSON'). It also names nearby siblings (vc_page_markdown, pay) and the private-vs-public distinction, so an agent can tell it apart without opening schemas.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('current public web results for a query'), an explicit exclusion ('Do not use for private/intranet pages'), and the replacement call ('vc_page_markdown with a known URL'). The sibling note further disambiguates vc_page_markdown vs pay.

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

All Vibes-Coded Agent Security and Commerce Tools 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.8/5.0
Disambiguation4/5

Most tools target a clearly distinct resource and action: notepad save/read/list/share/browse is cleanly separated from workspace create/read/write/list, and pairs like vc_web_search vs vc_page_markdown have explicit boundaries. The four guard tools (state, drift, idempotency, retry storm) share the same advisory-preflight pattern and could be confused at a glance, though their differing nouns and sibling cross-references reduce misselection.

Naming Consistency4/5

The vc_<domain>_<action> convention with the action verb last is consistent across most tools (v_c_notepad_save, v_c_workspace_create, v_c_square_post, v_c_drift_guard, v_c_attest_verify). Two platform tools break the pattern — health (bare noun) and pay (bare verb with no vc_ prefix) — and a few names like v_c_agent_reputation and v_c_page_markdown are noun-only, creating minor inconsistency.

Tool Count3/5

At 26 tools, the server sits just above the heavy range, but the surface spans eight distinct subdomains (guards, attestation, skill scanning, notepad memory, workspaces, town square, web search/fetch, payments), so most tools earn their place. The aggregate surface is still large for an agent to navigate and could benefit from splitting security, commerce, and memory/workspace into separate servers.

Completeness3/5

Core workflows are well covered: attest/verify, notepad save/read/list/share, workspace create/read/write/list, search/fetch, skill scan/consensus, and pay/watch. Notable gaps exist — there is no delete for notepad notes or workspaces, no way to remove a marketplace listing, and no attestation revoke — leaving the memory and workspace lifecyles incomplete.

Resources