Vibes-Coded Agent Tools

vc_marketplace_search

Read-onlyIdempotent

Search the Vibes-Coded marketplace for AI-agent tools and API outcomes.

    Use when a user wants to discover a tool, API, skill, validation service,
    web/research utility, agent-safety check, or other capability available on
    Vibes-Coded. Search by the user's actual task and return relevant listings.

    This tool only searches Vibes-Coded's bounded marketplace catalog. It does
    not execute a paid outcome, change user data, or search the general web.
    Prefer this before `pay` when the user has not already chosen a specific
    Vibes-Coded outcome.

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

Input Schema

Name	Required	Description
`query`	Yes	What the user wants to accomplish, e.g. 'repair malformed JSON', 'verify an agent completed a deployment', or 'search the web'.
`category`	No	Optional marketplace category filter.
`free_only`	No	Only return resources that are free or explicitly marked free-tier.
`max_results`	No	Maximum matches to return, from 1 to 20.
`max_price_usd`	No	Optional maximum listed USD price per call.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 29, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false. The description adds substantive context beyond that: the catalog is 'bounded' (matching openWorldHint=false), it does not execute paid outcomes, and it does not mutate user data. It stops short of describing result payload behavior, but the output schema covers that.

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?

Front-loads the core purpose in the first sentence and then layers exclusions and routing guidance. It is a bit longer than strictly necessary for a search tool, but each sentence carries distinct information and nothing is redundant.

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 annotations covering the safety profile, the description supplies everything else an agent needs: catalog scope, non-execution semantics, and routing relative to pay. No gaps remain for correct invocation.

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 every parameter is already documented in the schema, including the query examples and max_results range. The description adds no parameter-level detail beyond what the schema provides, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb (search) and resource (Vibes-Coded marketplace for AI-agent tools and API outcomes), and enumerates the kinds of capabilities found (tool, API, skill, validation service, web/research utility, agent-safety check). This clearly distinguishes it from vc_web_search and pay.

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?

Explicitly states when to use it, what it is not (does not execute a paid outcome, change user data, or search the general web), and routes the agent with 'Prefer this before `pay` when the user has not already chosen a specific Vibes-Coded outcome.' This is full when/when-not/alternative guidance.

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 Tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.