SCVD General Store

Check purchase status

check_purchase

Read-onlyIdempotent

Use recovery.purchase_id and private recovery.status_token to read payment, original terms and available fulfillment, even after payment expiry. Free; submits no payment. Fulfillment may contain a recovered instant good or human order; human work remains pending until completed. Payment alone is not proof of delivery.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`purchase_id`	Yes	The recovery.purchase_id from your purchase response.
`status_token`	Yes	The private recovery.status_token from the purchase response.

Output Schema

TableJSON Schema

Name	Required	Description
`terms`	No
`charged`	No
`request`	No	The full original request.
`fulfillment`	No	Recovered purchase response, when available.
`purchase_id`	No	The original purchase identifier.
`payment_state`	No	The recorded payment outcome.
`delivery_state`	No	Whether the good is delivered, a human order exists, or delivery is not yet established.

Schema Changelog

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

Changed2 schema fields changedSep 7, 2026

changedOutput schema / properties / delivery_state / description

Previous value: -"This payment record alone does not establish delivery."New value: +"Whether the good is delivered, a human order exists, or delivery is not yet established."

addedOutput schema / properties / fulfillment

Added value: +{
+  "description": "Recovered purchase response, when available.",
+  "type": "object"
+}

AddedSep 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations by stating it is free, submits no payment, and clarifying that fulfillment may involve instant goods or pending human work. No contradictions with annotations.

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 compact, front-loaded with the main action, and every sentence adds relevant information. It avoids redundant phrasing and keeps the essential context in three tight sentences.

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?

The description covers the purpose, temporal edge case of payment expiry, fulfillment types, and a practical warning about delivery proof. It does not detail output schema contents, but the presence of an output schema is noted and the description sufficiently frames what the tool returns.

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?

Both parameters are fully covered by the schema with clear descriptions referencing the recovery purchase_id and private status_token. The tool description repeats this but does not add significant extra meaning beyond the schema, so it meets the baseline for high schema coverage.

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 title and description clearly state the tool reads purchase status, including payment, terms, and fulfillment. It explicitly says 'submits no payment,' distinguishing it from the buy_* sibling tools and making its read-only purpose unmistakable.

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 provides clear guidance on when to use it: with recovery.purchase_id and status_token, even after payment expiry. It also advises that payment alone is not proof of delivery. It does not explicitly name sibling alternatives like check_order or check_before_you_pay, so it falls short of fully explicit when-not-to-use guidance.

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

All SCVD General Store tools Inspect

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.