Skip to main content
Glama

Shipping Carrier Options Get

tiendanube_shipping_carrier_options_get
Read-onlyIdempotent

Retrieve details of a specific shipping carrier option by carrier ID and option ID to view available shipping methods and their configurations.

Instructions

Get one carrier option. HTTP: GET /shipping_carriers/{carrier_id}/options/{option_id} Required scope: read_shipping API version: 2025-03

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": {
      "carrier_id": "<carrier_id>",
      "option_id": "<option_id>"
    },
    "name": "tiendanube_shipping_carrier_options_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated list of fields to return, to reduce payload size (e.g. 'id,name,variants')
option_idYesOption ID
carrier_idYesShipping carrier ID
response_formatNoOutput format: 'json' (default, full data) or 'markdown' (human-readable)json

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds genuinely useful context beyond that — the required OAuth scope read_shipping and the API version 2025-03 — but says nothing about behavior on missing IDs (404 vs empty) or the shape of the returned payload.

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?

Four short lines, front-loaded with the verb and resource, then the endpoint, scope and version. No filler, no restatement of the title, and the constraint metadata is placed where an agent will see it first.

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?

For a simple read-only single-resource fetch with full schema coverage, complete annotations and no output schema, the description supplies everything needed to invoke it correctly. The one small gap is that it does not hint at what a carrier option contains, leaving the agent dependent on the raw response.

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 description coverage is 100%, so all four parameters (carrier_id, option_id, fields, response_format) are already documented, which sets the baseline at 3. The description slightly exceeds baseline by embedding the path template that shows exactly where carrier_id and option_id are substituted.

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?

States a specific verb and resource ('Get one carrier option') and pins the exact endpoint GET /shipping_carriers/{carrier_id}/options/{option_id}, which makes clear it fetches a single option rather than a list. It does not explicitly name tiendanube_shipping_carrier_options_list as the alternative, but the singular/'one' phrasing and the ID-keyed path differentiate it adequately.

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 by the required IDs and the single-object framing, so an agent can infer it is for retrieving one known option. There is no explicit when-to-use / when-not-to-use guidance and no mention of the list sibling for discovery, and the required scope is stated as a fact rather than an actionable prerequisite caveat.

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

Deploy Server

Other Tools