YappyKids shop

get_delivery_options

Delivery methods and prices for a destination country and an order. Pass the product ids (with quantities) to get the shipping weight and order total computed from current prices, or pass order_total and weight_kg directly.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_delivery_options"
  }
}

Input Schema

Name	Required	Description
`lang`	No	Shop language: lv, lt, ee, pl, de, en, fr, ru. Defaults to the language of the domain the request was sent to.
`items`	No	Products in the order
`country`	No	ISO 3166-1 alpha-2 country code, e.g. LV, LT, EE, PL, DE, FR. Defaults to the shop language's country.
`weight_kg`	No	Total weight in kg, used if items are not given.
`order_total`	No	Order total in shop currency, used if items are not given.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden. It discloses that pricing is derived from current catalog prices and that weight/total can be computed or supplied, but it says nothing about whether this is a pure read, currency/VAT treatment, or failure modes for unsupported destinations.

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?

Two sentences, purpose front-loaded, no filler. The second sentence is slightly dense in bundling both calling modes, but every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five optional parameters, no annotations, and no output schema, the description should do more: it does not describe the returned delivery-method/price structure, currency, or what happens when country or items are omitted (beyond schema defaults). Adequate for invocation, incomplete for interpretation.

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 each parameter is already documented, including the 'used if items are not given' fallback for weight_kg and order_total. The description reinforces the items-vs-manual-values choice and adds 'computed from current prices', but adds little else beyond 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?

The description names a concrete resource and output (delivery methods and prices) scoped to a destination country and an order, which is distinct from the sibling tools (availability, product lookup, store info). It does not explicitly name a sibling to rule out, so it stops 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?

It clearly explains the two calling modes: pass product ids with quantities to have weight and order total computed, or pass order_total and weight_kg directly. That is actionable routing between parameter paths, though it gives no exclusions or preconditions (e.g. what happens with an unsupported country).

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

All YappyKids shop 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?