Skip to main content
Glama
Sign In
agent-pay-gate

agent-pay-gate

by NariP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Request payment approval

request_payment

Create a PayPal payment request for a quote and return an approval link for the human to review. Use it when an agent needs a checkout link but cannot approve or pay.

Instructions

Create a PayPal payment request for a quote and get an approval link for the human. You cannot approve or pay it yourself: give the link to the user and wait. Do not open the link or try to complete checkout.

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": {
      "quote_id": "<quote_id>"
    },
    "name": "request_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that a real PayPal payment request is created, that the agent lacks approval/pay authority, and that the agent must wait rather than act. It does not cover prerequisites such as PayPal account/auth requirements, link expiry, idempotency for an existing request on the same quote, or what happens if the human declines.

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?

Three short sentences, action stated first, then the human-in-the-loop constraint, then the prohibitions. No filler and no repetition.

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?

For a one-parameter tool with no output schema, the description covers the essential contract: what is created, what the caller receives (an approval link), and what the caller must and must not do with it. Remaining gaps are edge-case handling (expiry, re-request, declined approval) rather than anything needed to call it correctly the first time.

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?

There is one required parameter at 0% schema description coverage. The phrase "for a quote" implies quote_id is the quote to be paid, but the description never explains the identifier's expected form or where it comes from (presumably create_quote). Minor but real gap for a single-param tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Create a PayPal payment request for a quote and get an approval link" names a specific verb, resource, payment provider, and the concrete artifact produced. It does not explicitly contrast with siblings like check_payment, so the agent must infer that this initiates while the sibling inspects.

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?

The description is clear about the operating context: hand the link to the human and wait, and explicitly do not open the link or attempt checkout. It states exclusions well but never names an alternative tool for checking approval status after the link is issued, leaving that handoff to inference.

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

Deploy Server

Other Tools