Skip to main content
Glama
ByteBunny-io

nanocart-mcp

by ByteBunny-io

update_vendor

Partially update a fulfillment vendor, preserving unspecified fields and the saved template. Set status to paused/active to pause or resume order emails.

Instructions

Update a fulfillment vendor (partial — provide only the fields to change; the rest are preserved, including the saved template). Use status "paused"/"active" to pause or resume order emails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNo
toNoRecipient email addresses (1-5)
nameNo
notesNoStanding instructions sent with every order via {{vendor.notes}}
statusNopaused = new orders are skipped (recorded on the order) until resumed
vendorIdYes
template_htmlNoCustom order-sheet HTML (max 50KB). Empty = the standard sheet. Custom HTML MUST contain {{items_table}} or an {{#items}}…{{/items}} block or the API returns NO_ITEMS_PLACEHOLDER. There are NO price tags.
include_shippingNoFill {{shipping_address}} with the customer ship-to (default true)
subject_templateNoSubject line; {{order.number}} {{store.name}} {{vendor.name}} resolve
include_customer_contactNoFill {{customer.name}}/{{customer.email}} (default false)
Behavior4/5

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

The description adds behavioral context beyond the neutral annotations (all false) by explaining partial-update semantics and that unspecified fields are preserved, including the template. It also discloses the effect of the status parameter on order emails. No contradiction with annotations.

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?

The description is very concise, consisting of two sentences that deliver the core functional details without redundancy. It is appropriately front-loaded with the action and key partial-update caveat.

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?

Given the tool has 10 parameters and no output schema, the description is reasonably complete. It covers the essential update semantics and status usage, while the schema handles parameter details. It does not mention return values, but that's not a significant gap for an update tool.

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?

The schema covers 70% of parameters with descriptions. The description adds value for status behavior and template preservation, but it does not compensate for the undocumented parameters (cc, name, vendorId). It's above the baseline for 70% coverage but not fully comprehensive.

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?

The description clearly states the action ('Update a fulfillment vendor') and includes the key distinction of partial updates, which differentiates it from create_vendor and delete_vendor. The mention of preserving unspecified fields and the saved template further clarifies its scope.

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?

The description implies when to use this tool (for modifying an existing vendor) through 'partial — provide only the fields to change' and 'the rest are preserved'. It also gives a specific usage example for status to pause/resume order emails. However, it does not explicitly exclude alternatives or state when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ByteBunny-io/nanocart-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server