Pinoyshki Bakery

Browse the Pinoyshki menu

get_menu

Read-onlyIdempotent

Pinoyshki Bakery's menu with prices and photos, from the bakery's live data. lane 'today' is today's counter menu (what can be ordered on Toast for pickup today or a later day; sold-out items are left off); lane 'catering' is the catalogue for ordering 3 days to a week ahead, with sizes (full-size, bite-size dozen, half dozen).

Input Schema

Name	Required	Description
`lane`	No	Default 'today'.
`section`	No	Optional section filter, like 'Pastries' or 'Vegan'. 'Piroshki' and 'Pinoyshki' both show the whole family (pinoyshki are piroshki with Filipino fillings); customers asking for either nearly always want both.
`only_this_family`	No	Only when the customer asked for just piroshki or just pinoyshki: keep the section filter to that word.

Output Schema

Name	Required	Description	Default
`lane`	No
`note`	No
`view`	Yes
`hours`	No
`title`	Yes
`sections`	Yes
`closed_weekdays`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 25, 2026

addedInput schema / properties / only_this_family

Added value: +{
+  "description": "Only when the customer asked for just piroshki or just pinoyshki: keep the section filter to that word.",
+  "type": "boolean"
+}

changedInput schema / properties / section / description

Previous value: -"Optional section filter, like 'Pastries' or 'Piroshki'."New value: +"Optional section filter, like 'Pastries' or 'Vegan'. 'Piroshki' and 'Pinoyshki' both show the whole family (pinoyshki are piroshki with Filipino fillings); customers asking for either nearly always want both."

First observedSep 25, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: data is live, sold-out items are omitted from the 'today' lane, and catering carries size variants.

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 dense sentence with the resource and data source front-loaded, followed by lane semantics. Every clause carries information, though the parenthetical detail in the lane clause makes it slightly heavy.

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?

An output schema exists, so return values need no description, and annotations cover the safety profile. The description closes the remaining gaps (lane selection, section filtering, family merging), leaving only sibling-level routing unaddressed.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description goes further by explaining what each lane actually returns and the rationale for the Piroshki/Pinoyshki family merge, adding meaning beyond the schema's terse field descriptions (though only_this_family guidance largely restates the schema).

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+resource ('Pinoyshki Bakery's menu with prices and photos, from the bakery's live data') and defines the two lanes precisely. It is clear on its own, but does not explicitly differentiate itself from siblings like search_menu or show_item, so it falls short of a 5.

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?

Gives explicit when-to-use conditions for the two lanes: 'today' for counter pickup today or later, 'catering' for ordering 3 days to a week ahead. No sibling alternatives or exclusions are named, so it stops short of a 5.

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?