Pinoyshki Bakery

Get the checkout link

start_checkout

Only after check_order came back allowed and the customer confirmed the lines and subtotal: checks the same order again and returns the link the customer pays on. Same day: the bakery's order page with the tray loaded and a Pay with Toast button (good for 3 hours). Catering: the Pinoyshki cart with the date, time and pickup or delivery filled in. No payment happens here. If a rule is broken it returns the problems instead of a link.

Input Schema

TableJSON Schema

Name	Required	Description
`zip`	No	Delivery ZIP code (delivery is within 15 miles).
`date`	No	The date as YYYY-MM-DD ('today' also works). Work it out from the customer's words using today's date in Seattle (Pacific time). If their words could mean two dates, like 'next Friday' said earlier in the same week, ask them which before calling. Needed for catering.
`time`	No	12-hour time like '1:00 pm'. Needed for catering.
`items`	Yes	What to order. Use item names exactly as get_menu or search_menu gave them.
`notes`	No	Optional note for the bakery.
`channel`	No	Optional. 'today' = same day from the counter menu, paid on Toast; 'catering' = ordered ahead, paid on Shopify. Left out, the basket decides.
`utensils`	No	Catering: include utensils. Default true.
`fulfillment`	No	Default pickup. Delivery is catering, week-ahead only.
`customer_name`	No	Optional: the name the order is for.
`customer_email`	No	Optional: an email for the bakery.
`customer_phone`	No	Optional: a phone number for the bakery.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	True when the order is allowed as asked.
`url`	Yes	The link the customer opens to pay. Give it to them as-is.
`view`	Yes
`when`	No
`lines`	Yes
`title`	No
`today`	No	Today's date in Seattle, like 'Thursday, September 24'.
`button`	No
`channel`	No
`pays_on`	No
`problems`	No
`lane_label`	No
`date_choices`	No	Present when the date asked for could mean either of these; ask the customer which.
`allowed_dates`	No
`allowed_times`	No
`earliest_date`	No
`subtotal_cents`	Yes	Before tax; the checkout page shows the final total.
`delivery_allowed`	No
`allowed_date_labels`	No	allowed_dates with weekdays, like 'Fri Oct 2'.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 25, 2026

changedInput schema / properties / date / description

Previous value: -"YYYY-MM-DD, 'today', or plain words like 'next Friday'. Needed for catering."New value: +"The date as YYYY-MM-DD ('today' also works). Work it out from the customer's words using today's date in Seattle (Pacific time). If their words could mean two dates, like 'next Friday' said earlier in the same week, ask them which before calling. Needed for catering."

addedOutput schema / properties / allowed_date_labels

Added value: +{
+  "description": "allowed_dates with weekdays, like 'Fri Oct 2'.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / date_choices

Added value: +{
+  "description": "Present when the date asked for could mean either of these; ask the customer which.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / today

Added value: +{
+  "description": "Today's date in Seattle, like 'Thursday, September 24'.",
+  "type": "string"
+}

First observedSep 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, the description discloses that no payment happens, that same-day links expire after 3 hours, that the order is re-validated, and that rule violations return problems rather than a link. This gives the agent a strong model of side effects and failure outcomes.

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?

The description is information-dense and front-loaded with the precondition, and the same-day/catering contrast is efficient. It is slightly long and contains some redundancy ('checks the same order again' after mentioning check_order), but it is not padded.

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?

For a complex 11-parameter tool with an output schema, the description covers the workflow gate, channel variants, link validity, no-payment behavior, and failure mode. There is no missing context an agent needs to decide whether and how to call it.

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?

The input schema already documents all 11 parameters with 100% coverage, so the description need not repeat them. It adds contextual flavor for date/time/fulfillment in catering but no parameter-level detail beyond the schema, matching the baseline for full 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 description states a specific action ('checks the same order again and returns the link the customer pays on') and a clear resource, distinguishing it from check_order. The same-day/catering branches make the tool's function concrete without ambiguity.

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?

The opening clause gives an explicit precondition: only call after check_order returned allowed and the customer confirmed lines/subtotal. It also states the failure behavior (returns problems instead of a link), which tells the agent when the result is not usable.

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

All Pinoyshki Bakery tools Inspect

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

Need Help?