Skip to main content
Glama
Sign In

NodajiMarket

by com.nodajimarket
OverviewDiscussionsAdmin

Estimate delivered cost

nodajimarket_get_landed_cost
Read-onlyIdempotent

Delivered (landed) cost for up to 10 products to one destination: items, shipping, duties estimate, tax and the DDP total in USD cents — the same numbers the store's own checkout charges. For Canada the card is charged in CAD at a fixed rate; charged.amountCents shows that. Returns supported:false with a message for destinations we do not ship to (South Korea, sanctioned countries).

Input Schema

NameRequiredDescriptionDefault
ship_toYesDestination country, ISO 3166-1 alpha-2 (CA, US, JP)
quantitiesNoSame length as product_ids; default 1 each
postal_codeNoDestination postal code — for Canada it sets the provincial tax rate
product_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / postal_code
      Added value: +{
+  "description": "Destination postal code — for Canada it sets the provincial tax rate",
+  "maxLength": 10,
+  "minLength": 3,
+  "type": "string"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive safety, and the description goes further by disclosing the unsupported-destination behavior (supported:false, South Korea/sanctioned countries) and the CAD fixed-rate charging quirk with charged.amountCents. That is genuinely useful behavior beyond the annotations.

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 dense, front-loaded sentences covering scope, output contents, and edge cases. There is a slightly garbled fragment ('charged.amountCents shows that') but no wasted sentences.

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?

With no output schema, the description compensates by listing the returned fields (items, shipping, duties, tax, DDP total, supported flag, amountCents). Complete enough for an agent to call and interpret the result, though postal_code's optional role could be restated.

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 coverage is 75% and the schema already documents ship_to format, postal_code's tax role, and quantities defaults. The description only adds the 10-product ceiling, so it does little beyond the schema — baseline 3 is appropriate.

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+resource ('Delivered (landed) cost') plus scope (up to 10 products, one destination) and enumerates the computed components. It is clearly distinct from siblings like create_checkout, get_product and search_products.

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?

The phrase 'the same numbers the store's own checkout charges' implies this is a cost-preview step relative to create_checkout, but no explicit when-to-use or when-not-to-use guidance is given. Usage is implied rather than stated.

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

All NodajiMarket 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