Vybe Pay MCP

List recent pays

list_recent_pays

Read-onlyIdempotent

List recent Collect pays, friend sends, and invoice pays started by the bound spend key, newest first. Filter by status: pending (waiting on Approve), paid (settled), or all. For paid Collect rows, call use_paid_offering with publicId. Related: pay_offering, pay_invoice, send_to_user, 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": "list_recent_pays"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of pays to return, from 1 to 40. Defaults to 20.
`status`	No	Which pays to return. pending = waiting on Approve, paid = settled, all = both. Defaults to all.	all

Output Schema

Name	Required	Description	Default
`pays`	Yes	Collect pays created by this spend key.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The annotations already cover read-only, idempotent and closed-world behavior, so the description only needs additive context. It adds the result ordering, the bound-spend-key scoping, and a concrete next-step for paid Collect rows, which go beyond the annotations. It omits any note on pagination beyond the limit parameter.

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?

Three compact sentences, front-loaded with the resource and scope, followed by filter semantics and routing. The trailing "Related:" list is useful for discovery but is a mild catalog dump rather than core instruction.

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?

With an output schema present, return values need no explanation, and the description covers scope, ordering, filtering, and follow-up action. Minor gaps remain around pagination behavior and what the "bound spend key" requires to be configured.

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%, so the baseline is 3. The description largely restates the status meanings that already appear in the schema ("pending = waiting on Approve") and says nothing about limit, so it adds little meaning beyond the schema.

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?

The description uses a specific verb and resource ("List recent Collect pays, friend sends, and invoice pays"), states the scope ("started by the bound spend key") and the ordering ("newest first"). That is enough to separate it from siblings such as list_invoices or pay_offering without opening a schema.

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

Usage Guidelines4/5

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

It explains the status filter values and gives explicit routing advice: "For paid Collect rows, call use_paid_offering with publicId." It also names related tools for adjacent actions. It does not state when to prefer a sibling like list_invoices, so a 4 rather than a 5.

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?