МылоПорошок — каталог mpshop.su

Ссылка на собранную корзину

create_cart_link

Read-only

Собрать корзину из найденных товаров и получить одну ссылку: покупатель открывает её и видит готовую корзину на mpshop.su. До 20 позиций. Ничего не заказывает и не оплачивает — только формирует ссылку.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "items": "<items>"
    },
    "name": "create_cart_link"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes	Позиции корзины, до 20 штук.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description adds important behavioral context: 'Ничего не заказывает и не оплачивает — только формирует ссылку.' This reassures the agent no order or payment occurs, beyond what annotations provide, though it lacks details on link expiration or persistence.

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?

Three short sentences with zero waste, front-loading the core action and outcome, then limits and non-actions. Every sentence is purposeful.

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?

Given the single nested parameter, rich schema coverage, and annotations, the description is complete enough: it states what the tool does, the limit, and what it does not do. It could mention output details or link validity, but with no output schema that is a minor gap.

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%, so the schema fully documents the items, product_id, and quantity parameters. The description only repeats the constraint 'До 20 позиций' without adding new semantic meaning beyond the schema's maxItems.

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 verb and resource: 'Собрать корзину из найденных товаров' and produces 'одну ссылку' to mpshop.su. This clearly distinguishes it from read-only catalog siblings like search_products or get_product, which do not assemble a cart.

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?

It contextualizes usage by saying it works with 'найденных товаров' (previously found products) and clarifies the deliverable is a link for a customer, implying the shopping workflow. It does not explicitly name alternatives or when-not-to-use, but the context is clear.

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

All МылоПорошок — каталог mpshop.su 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?