Vybe Pay MCP

Run free marketplace tool

run_free_tool

Run a free tool from the Vybe Marketplace and get its answer. No sign-in or spend key needed, and nothing is charged. Get the slug, action names and inputs from search_tools or get_tool first. Free tools have fair-use limits per caller; if you hit one, tell the user when it resets. Paid tools can't run here: use pay_offering and use_paid_offering. Related: search_tools, get_tool.

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": {
      "slug": "<slug>"
    },
    "name": "run_free_tool"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	Tool slug from search_tools or get_tool.
`toolName`	No	Action name from get_tool. Optional when the tool has one action.
`toolArguments`	No	The action's inputs as JSON, using the keys from get_tool.

Output Schema

Name	Required	Description
`ms`	No
`ok`	Yes
`code`	No
`tool`	No
`action`	No
`result`	No	What the tool returned.
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well past the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false, idempotentHint=false) by disclosing that no sign-in or spend key is required, that nothing is charged, and that free tools carry per-caller fair-use limits with a reset time to report to the user — exactly the operational facts an agent cannot infer from 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?

Front-loaded with the core action and cost/auth facts, then prerequisites, then limits, then the exclusion. The trailing "Related: search_tools, get_tool" duplicates the prerequisite sentence and is the one line that doesn't earn its place.

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?

An output schema exists so return values need no explanation, and the description covers auth, cost, rate limits, prerequisites, and the paid/free boundary. The only thin spot is error behavior for an unknown slug or a missing toolName on a multi-action tool, which is left implicit.

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 slug, toolName, and toolArguments are already documented, and the description largely restates the same sourcing advice ("Get the slug, action names and inputs from search_tools or get_tool") rather than adding new meaning. It does not clarify argument-key conventions or what to do when toolArguments keys are unknown, so baseline 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?

States a specific verb and resource ("Run a free tool from the Vybe Marketplace and get its answer") and immediately bounds the scope with "Paid tools can't run here," which cleanly separates it from pay_offering and use_paid_offering among the siblings.

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 prerequisite chain (get slug/action names/inputs from search_tools or get_tool first), an explicit exclusion with named alternatives (pay_offering, use_paid_offering for paid tools), and even handling advice for the fair-use limit case.

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

All Vybe Pay MCP 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.

Resources

Need Help?