Skip to main content
Glama

Synchronity

by io.github.themewireco

get_payment_status

Read-only

FINAL STEP of the in-chat payment flow. Returns the current PaymentSession for an order. Poll this (every ~5 seconds) after initiate_payment/submit_payment_otp until payment_status becomes "paid" or "processing" (success — the order is confirmed) or "failed" (tell the user; they can retry by initiating a new payment). Do NOT treat the purchase as complete until this returns "paid" or "processing". No delegation needed (read-only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idNoRegistered site ID (optional if DEFAULT_SITE_ID is set)
order_idYesOrder ID to check payment status for

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageNo
referenceNo
instructionNo
payment_statusNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Discloses polling behavior and status interpretation beyond annotations (readOnlyHint=true). The description explicitly states 'No delegation needed (read-only),' reinforcing the safe read nature. No contradictory behaviors are present.

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?

The description is a single dense paragraph with every sentence adding value. It front-loads the core purpose ('FINAL STEP') and presents polling frequency, conditions, and actions concisely. No wasted words.

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?

Given the tool's role in a multi-step payment flow and the presence of an output schema, the description covers all necessary context: polling interval, success/failure conditions, user instructions, and safety. It fully addresses the complexity without missing critical details.

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% (both parameters have descriptions). The description does not add new meaning to the parameters beyond the schema; it does not mention site_id at all. Baseline 3 is appropriate as the description focuses on usage flow rather than parameter details.

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 clearly states the tool is the 'FINAL STEP' of the payment flow and returns the current PaymentSession for an order. It uses specific verbs ('returns', 'poll') and distinguishes it from sibling tools like initiate_payment and submit_payment_otp by positioning it as the polling step to check the outcome.

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?

Provides explicit when-to-use guidance: poll every ~5 seconds after initiate_payment/submit_payment_otp. Defines success conditions ('paid' or 'processing') and failure condition ('failed'), including user messaging. Also specifies not to treat purchase as complete until these statuses are met, and notes no delegation is needed.

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

All Synchronity toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct action or resource, with detailed descriptions that clearly differentiate cart management, checkout flow, payment steps, delegation, orders, and product operations. Potential overlaps like get_active_cart vs. get_cart are resolved by their specific use cases.

Naming Consistency5/5

All tools use a consistent verb_noun_snake_case pattern (e.g., add_to_cart, set_shipping_address). There are no mixing of conventions like camelCase or inconsistent verb styles.

Tool Count4/5

26 tools is on the higher side but appropriate for a comprehensive e-commerce server covering product discovery, cart management, checkout, payment, orders, and reviews. Could potentially be streamlined slightly, but still reasonable.

Completeness5/5

The tool set covers the full e-commerce lifecycle: site listing, product search/compare/reviews, cart CRUD, coupon application, shipping, checkout, payment with delegation and OTP, order retrieval, and back-in-stock alerts. No obvious gaps for typical buyer workflows.

Resources