Skip to main content
Glama

Mark Physical Product Order Shipped

mark_physical_product_order_shipped

Mark a physical product order as shipped. Requires confirm set to SHIP. Before offering this action or requesting its inputs, check business permissions. FREE businesses cannot use this tool, regardless of individual feature rows. Call check_business_tool_access before collecting inputs. Show any grace-period warning and verified resubscribe link before continuing, and never proceed when access is blocked.

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": {
      "communityId": "<communityId>",
      "orderId": "<orderId>"
    },
    "name": "mark_physical_product_order_shipped"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
confirmNoExplicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action.
orderIdYesPhysical product order ID.
communityIdYesNas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one.
trackingNumberNo
shippingProviderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / communityId / description
      Added value: +"Nas.com business (community) ID. Use an ID returned by list_businesses or another Nas.com tool; never invent one."
    • addedInput schema / properties / confirm / description
      Added value: +"Explicit confirmation for this write. Pass the exact literal this tool requires (for example DELETE) only after the user approves the action."
    • addedInput schema / properties / orderId / description
      Added value: +"Physical product order ID."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations only declare non-read-only, non-destructive, non-open-world; the description adds real behavioral context on top: a required confirmation literal, entitlement gating by business tier, a mandatory access-check prerequisite, and grace-period warning handling. It omits downstream effects (customer notification, order status transitions, tracking requirement), so it is not fully complete.

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?

The action is front-loaded in the first sentence, followed by prerequisite gating, which is the right order. The permission requirement is stated twice in slightly different words ('check business permissions' and 'call check_business_tool_access before collecting inputs'), a minor redundancy.

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?

For a six-parameter mutation with no output schema and sparse annotations, the gating and confirmation behavior is well covered, but the description leaves gaps: it doesn't say what the call changes beyond shipment status, whether trackingNumber or shippingProvider are required, or what is returned. Adequate for safe invocation, not fully complete.

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?

At 50% schema coverage, three parameters (notes, trackingNumber, shippingProvider) carry no description in either the schema or the prose. The description does add valuable specificity for confirm by pinning it to the literal SHIP rather than the schema's generic 'for example DELETE', but it does not explain the shipping fields or whether they are optional or required.

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 opens with a specific verb and resource: 'Mark a physical product order as shipped,' which is unambiguous and distinct from siblings such as list_physical_product_pending_shipments or get_physical_product_order. It does not explicitly name a sibling it replaces or redirect to, 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 gives clear preconditions: confirm must be the literal SHIP, business permissions must be checked first, and check_business_tool_access must be called before collecting inputs. It also states a hard exclusion (FREE businesses cannot use it, regardless of feature rows). It does not address alternatives for fulfilling or updating an order, which keeps it at 4.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources