Vybe Pay MCP

Get marketplace tool

get_tool

Read-onlyIdempotent

Full details for one marketplace tool: actions with their inputs, an example, price, seller and health, plus the exact next step. For a paid tool the next step is pay_offering with its offeringUrl, then use_paid_offering with toolName and toolArguments. For a free tool it is run_free_tool, which needs no sign-in. Pass slug or the tool page URL. Related: search_tools, run_free_tool, pay_offering, use_paid_offering.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_tool"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Tool page URL, e.g. https://www.vybe.finance/marketplace/tools/pathguard.
`slug`	No	Tool slug from search_tools, e.g. pathguard.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`code`	No
`tool`	No
`message`	No
`nextAction`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 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 closed-world, so the safety profile is covered. The description adds real value beyond that by explaining the retrieved 'health' field and the mandatory downstream call sequence, including the no-sign-in property of the free path. It stops short of describing failure behavior for an unknown slug or an invalid URL.

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 payload contents before the routing details, and every clause carries information. The workflow sentence is dense and slightly run-on, but nothing is wasted.

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?

For a read-only lookup with full annotation coverage, a complete input schema, and an output schema, the description covers the remaining gaps: what fields are returned and which tool to call next in each pricing scenario. Nothing needed to invoke 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 coverage is 100% and the schema already defines both slug and url with examples plus the 'Provide slug or url' note. The description's 'Pass slug or the tool page URL' restates the schema without adding precedence rules (e.g., which wins if both are supplied), 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 ('Full details for one marketplace tool') and enumerates exactly what comes back: actions with inputs, example, price, seller, health, and the next step. It is clearly distinguishable from the sibling search_tools, which returns a list rather than one tool's full record.

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 routing table: paid tools route to pay_offering with offeringUrl, then use_paid_offering with toolName and toolArguments; free tools route to run_free_tool with no sign-in. It also names the accepted inputs and lists related tools, leaving little to inference.

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?