Skip to main content
Glama
Sign In

1lev1

by io.github.Avi-ADAM
OverviewDiscussionsAdmin

quoteShippingTool

Read-onlyIdempotent

Price delivery of a cart from one rikma to an address — "how much is delivery to Haifa?". Give the products (and variant when the product has variants) with quantities, and the address (city is enough inside Israel; the district is resolved from it). Unit prices are read from the rikma's own catalog, so free-delivery thresholds apply as at checkout. Returns every option (delivery methods, pickup points, digital, "contact the seller") with fee, whether it is free, how much more makes it free, ETA and next dispatch day, plus why delivery is unavailable (outsideZones, noDeliveryProducts, needsAddress, weightUnknown). Members only; read-only — nothing is ordered. Docs: https://1lev1.com/mcp#quoteShippingTool

Input Schema

NameRequiredDescriptionDefault
itemsYesWhat is being sent.
addressNoWhere it goes. Omit to see pickup/digital options and which methods would need an address.
projectIdYesRikma (project) id, from findUserProjectsTool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / items / items / properties / variantId / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / items / items / properties / variantId / type
      Added value: +[
+  "string",
+  "null"
+]
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), it discloses that pricing is read from the rikma's own catalog so free-delivery thresholds apply as at checkout, that the district is resolved from the city, that membership is required, and enumerates the unavailability reasons returned. This is substantive behavioral context the annotations alone cannot convey.

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?

Front-loaded with the verb and a concrete example, with no filler sentences. It is a single dense paragraph packing in return-value and eligibility detail; readable but could be broken up for faster scanning.

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?

With no output schema, the description compensates fully by enumerating return content (options, fee, free flag, amount-to-free, ETA, dispatch day, unavailability reasons). Nested parameters (items, address) and the optional address path are both covered, so an agent has everything needed to call and interpret it.

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, but the description adds real meaning: productId/variant pairing from listRikmaProducts-style ids, quantity semantics, and the fact that a city alone is sufficient inside Israel. It stops short of documenting item limits or optional-field nuances beyond what the schema already states.

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?

States a specific verb and resource ('Price delivery of a cart from one rikma to an address') and grounds it with a concrete user question ('how much is delivery to Haifa?'). This clearly separates it from siblings like getShippingConfigTool (configuration) and listRikmaProductsTool (catalog lookup).

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 a clear usage context ('Members only; read-only — nothing is ordered') and explains the address requirement including the optional-address case for pickup/digital. It does not explicitly name alternative tools (e.g. getShippingConfigTool for config, searchCatalogTool for finding products), so routing is slightly inferred rather than spelled out.

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

All 1lev1 toolsInspect
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