Skip to main content
Glama
PayStage MCP Server

PayStage MCP Server

evaluate_mcp_payment

Evaluate an x402 PaymentRequired payload against a PayStage spending policy before payment to decide whether to pay, review, or block the transaction.

Instructions

Evaluate an x402 PaymentRequired payload against a PayStage spending policy before paying

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": {
      "payment_required": "<payment_required>"
    },
    "name": "evaluate_mcp_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyNo
policy_pathNo
payment_requiredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It communicates only that evaluation happens before paying; it does not say whether the call is read-only or whether it reserves/consumes spending budget, what decision (allow/deny) is returned, or how failures surface. For a spending-policy gate, the budget-consumption question is a critical undisclosed trait.

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?

A single front-loaded sentence with no filler; the pre-payment condition is placed at the end where it is still easy to find. It is efficient, though 'PayStage' is an undefined term packed into an otherwise tight line.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three parameters of which two are schema-less, no output schema, and no annotations, the description is too thin for the complexity. An agent still does not know the payload encoding, how policy vs policy_path interact, or what the evaluation returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

Schema description coverage is 0%, and two of three properties (policy, payment_required) have empty schemas, so the description must compensate. It only names the concepts ('PaymentRequired payload', 'spending policy') without explaining the expected format, or the crucial distinction between the inline 'policy' and the 'policy_path' file parameter.

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?

States a specific verb and object: 'Evaluate an x402 PaymentRequired payload against a PayStage spending policy'. The x402/PayStage terminology distinguishes it from siblings like evaluate_hip3_trade and evaluate_velocity without naming them, so an agent can tell which evaluation gate applies.

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

Usage Guidelines3/5

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

'before paying' gives an implied when-to-use: it is a pre-flight check prior to executing a payment. There is no explicit when-not, no mention of alternatives (e.g., whether a policy is required or what to do when none exists), and no prerequisite guidance.

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