Skip to main content
Glama

Paxaver

by com.paxaver.mcp
OverviewDiscussionsAdmin

Pay Lunch Order Draft

pay_lunch_order_draft

Commits a draft order from create_lunch_order_draft and charges the wallet for the item total plus optional tip_cents (donated to the school's PAC). Wallet-only: if the balance cannot cover the full total, the call fails with an error directing the user to open the Paxaver panel and top up the wallet balance, then retry - no card payment is offered through this tool. Not for new orders - use create_lunch_order_draft first. FINANCIAL - confirm the total before calling.

Input Schema

NameRequiredDescriptionDefault
order_idYesDraft order ID from create_lunch_order_draft - must still be in draft status; already-finalized orders are rejected
tip_centsNoTip in cents (donated to school PAC)

Output Schema

NameRequiredDescriptionDefault
statusNo'finalized' when the wallet covered the full total
orderIdNoOrder ID
tipCentsNoPAC donation added, in cents
itemTotalCentsNoItem total in cents

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed5 schema fields changed
    • removedOutput schema / properties / balanceCents
      Removed value: -{
-  "description": "Wallet balance after the charge, in cents",
-  "type": [
-    "number",
-    "null"
-  ]
-}
    • removedOutput schema / properties / id
      Removed value: -{
-  "description": "Order ID",
-  "type": "string"
-}
    • addedOutput schema / properties / orderId
      Added value: +{
+  "description": "Order ID",
+  "type": "string"
+}
    • changedOutput schema / properties / status / description
      Previous value: -"Order status (finalized)"New value: +"'finalized' when the wallet covered the full total"
    • removedOutput schema / properties / totalCents
      Removed value: -{
-  "description": "Total charged to the wallet, in cents",
-  "type": "integer"
-}
  4. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover the generic safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false); the description adds genuinely new behavior: wallet-only funding, the specific failure mode when balance is insufficient, the remediation path, and a financial confirmation warning. It goes well beyond what the structured fields disclose.

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?

Roughly four compact sentences, each carrying distinct load: action, payment mechanics, failure handling, prerequisite, and risk warning. The most important constraints (wallet-only, prerequisite) are front-loaded rather than buried.

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?

An output schema exists, so return values need not be described, and the description covers the remaining unknowns an agent needs: funding source, failure behavior, retry path, and the pre-call confirmation requirement. Nothing material is missing for a two-parameter mutation tool.

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 description coverage is 100% and both parameters are documented there, including the draft-status constraint on order_id and the PAC donation on tip_cents. The description restates the PAC donation and the 'total' concept but adds no syntax or format detail beyond the schema, 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 ('Commits a draft order ... and charges the wallet') and ties the input directly to the sibling that produces it (create_lunch_order_draft). An agent can distinguish this from create_lunch_order_draft, update_lunch_order_draft, and cancel_my_lunch_order without opening any schema.

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 explicit when-to-use ('commits a draft from create_lunch_order_draft'), when-not-to-use ('Not for new orders - use create_lunch_order_draft first'), and the failure/retry path (top up via the Paxaver panel, then retry). It also names the excluded alternative ('no card payment is offered through this tool').

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

All Paxaver toolsInspect
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