Vybe Pay MCP

Get spend limits

get_limits

Read-onlyIdempotent

Return the bound spend key’s hard limits: label, per-transaction max in USD, daily cap, optional seller allowlist, expiry, and authMode (oauth or vapt). Use this to tell the user what the agent is allowed to request before calling pay_offering. Related: get_spend_balance, get_wallet_balance.

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_limits"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`label`	No	Owner-chosen name for this key, e.g. Laptop agent.
`authMode`	No	How this MCP session authenticated.
`expiresAt`	No	ISO timestamp when this key expires, or null if it does not.
`clientName`	No	OAuth client name when authMode is oauth.
`dailyCapUsd`	No	Maximum USD per rolling 24 hours.
`perTxMaxUsd`	No	Maximum USD per pay_offering call.
`remainingDailyUsd`	No	Headroom left today under the daily cap.
`allowedSellerUsernames`	No	If non-empty, pay_offering may only target these Collect seller usernames.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare this read-only, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description still adds real context beyond them: the limits belong to the 'bound spend key', authMode distinguishes oauth from vapt credentials, and the seller allowlist is described as optional. It does not mention auth requirements or error behavior, but the schema does name the auth methods.

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?

Two sentences, with the returned fields front-loaded and the usage/precondition second, and both the `pay_offering` precondition and the sibling pointers are stated without extra wording. No sentence is redundant given the schema and annotations already present.

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 zero parameters, a full output schema, and rich annotations, the description covers what an agent still needs: what limits are returned, the authMode distinction, and when to call it relative to pay_offering. Nothing required 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning for the description to add and the baseline of 4 applies. The schema itself states that no arguments are accepted and describes the auth methods, leaving nothing undocumented.

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 ('Return the bound spend key's hard limits') and enumerates exactly what is returned: label, per-transaction max in USD, daily cap, seller allowlist, expiry, and authMode. It also names the sibling tools it relates to (get_spend_balance, get_wallet_balance), so an agent can place it in the family 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?

Usage is explicit: use it 'to tell the user what the agent is allowed to request before calling pay_offering', which gives a concrete trigger and ordering constraint. The related reads are listed as pointers but the description does not say when to prefer get_spend_balance or get_wallet_balance over this one, so the alternative-selection guidance is incomplete.

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?