Imperio Friki

prepare_checkout

Prepara un enlace temporal de revisión de cesta en Imperio Friki. El cliente revisa y añade los productos al carrito en la tienda antes de pagar. No crea pedidos ni ejecuta cobros.

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": "prepare_checkout"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes

Output Schema

Name	Required	Description	Default
`items`	Yes
`lines`	Yes
`notice`	Yes
`currency`	Yes
`shipping`	Yes
`checked_at`	Yes
`expires_at`	Yes
`final_total`	Yes
`checkout_url`	Yes
`reserves_stock`	Yes
`products_estimate`	Yes
`requires_customer_review`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations say readOnlyHint=false and idempotentHint=false, and the description usefully clarifies that no order is created and no charge is executed; in addition, it notes that the link is temporary. This materially reduces the agent's fear about what a non-read-only tool will do, though it does not state how long the link lasts or whether stock is reserved.

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, front-loaded with the action and resource, followed by the workflow and then the negative scope. Every sentence earns its place with no repetition.

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 format need not be explained, and the description covers the action, the workflow, and non-effects. It is close to complete; the only gap is the nature of the items payload, which the schema's constraints do not explain.

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

Parameters2/5

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

There is only one parameter, but items is a nested array with 0% schema description coverage, and the description says nothing about its structure, quantity limits (1–20 per item, 1–20 items), or what product_id must reference. The schema constrains but does not explain, and the description does not compensate.

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?

Names a specific verb and resource: it prepares a temporary cart-review link for Imperio Friki, with the customer adding products in the store before paying. It distinguishes itself from get_product/search_products, but does not explicitly differentiate itself from the sibling quote_cart, which sounds similar.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied — it is used as the pre-payment review step — and no explicit condition selects this tool over quote_cart, nor is there any mention of the prerequisites for sharing the link. An agent can infer the workflow, but the guidance is indirect.

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

All Imperio Friki 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?