Skip to main content
Glama
shi-kirill

pyaterochka-mcp

by shi-kirill
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

checkout_preview

Idempotent

Recalculates checkout totals, applies payment selections and loyalty discounts, then provides a preview of items and total for user confirmation before finalizing the order.

Instructions

Recalculate checkout and remember an immutable fingerprint.

Charges nothing, but may write payment selection, loyalty recalculation,
and revised prices to the shared upstream cart. Show the total and items to
the user; obtain an explicit confirmation before confirm_order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.5/5.0
Behavior4/5

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

Discloses that it may write to cart (payment selection, loyalty, prices) and that it charges nothing, adding context beyond annotations which only indicate idempotence and non-read-only.

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?

Two concise sentences with no wasted words; main action is front-loaded.

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 output schema exists, the description covers all necessary aspects: preview, side effects, user flow, and relation to confirm_order.

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?

No parameters; description adds meaning by explaining the tool's behavior, meeting the baseline of 4 for zero-parameter tools.

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?

Describes specific verb 'Recalculate checkout' with resource 'checkout' and mentions 'immutable fingerprint', clearly distinguishing from siblings like confirm_order.

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?

Explicitly states to use before confirm_order to show total and items to user, providing clear context for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shi-kirill/pyaterochka-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server