ActionShip by Teapplix Demo

Manage Shipping Profiles

teapplix_manage_shipping_profile

Create, read, update, or delete shipping profiles, dispatched by Operation (get/create/update/delete). Profiles define shipper address, return address, and carrier defaults for label generation. [DEMO]

Input Schema

TableJSON Schema

Name	Required	Description
`Active`	No	Active flag. Filter (get); default true (create); true/false to activate/deactivate (update).
`Address`	No	Shipper (ship-from) address printed on labels. Applies to create/update.
`Operation`	Yes	get: list/filter profiles. create: new profile (ProfileName required). update: modify profile (ProfileId or ProfileName required). delete: remove profile (ProfileId or ProfileName required).
`ProfileId`	No	Profile ID. Filter (get) or identifier (update/delete).
`Reference1`	No	Reference field 1. Applies to create/update.
`Reference2`	No	Reference field 2. Applies to create/update.
`Reference3`	No	Reference field 3. Applies to create/update.
`Reference4`	No	Reference field 4. Applies to create/update.
`ProfileName`	No	Profile name. Filter (get); required unique name (create); lookup or rename (update); identifier (delete).
`ReturnAddress`	No	Return address printed on labels. Defaults to Address if omitted. Applies to create/update.
`OnlyBill3rdParty`	No	When true, only bill 3rd party for carrier charges. Applies to create/update.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`Profiles`	No

TDQS

A3.6/5.0

Behavior1/5

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

The description explicitly lists 'delete' as an operation, but the annotations set destructiveHint to false, indicating the tool does not perform destructive side effects. This is a direct contradiction: deleting a profile is destructive. The description therefore does not provide reliable behavior disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short but redundant: it lists the operations twice ('Create, read, update, or delete' and 'get/create/update/delete'). The '[DEMO]' tag is unexplained and adds noise. It remains two sentences and front-loaded, but the redundancy and tag reduce clarity.

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 tool with 11 parameters, nested objects, and an output schema, the description gives sufficient high-level context about the tool's purpose and operation dispatch. The schema handles parameter details, and the output schema covers return values, so the description is complete enough for selection and basic invocation.

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?

With 100% schema coverage, the baseline is 3. The description adds value by clarifying that Operation selects the CRUD mode and by explaining that Address and ReturnAddress correspond to the shipper/return address definitions. This goes beyond the raw schema by linking parameter groups to domain concepts.

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 tool creates, reads, updates, or deletes shipping profiles, explicitly listing the operations get/create/update/delete. It distinguishes from sibling tools by focusing on shipping profiles and their role in label generation.

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 tells the agent to dispatch by Operation, which is the core usage pattern for this CRUD tool. It also explains that profiles define shipper address, return address, and carrier defaults, giving context for when this tool is relevant. It does not explicitly mention alternative tools, but the resource type is unambiguous.

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

All ActionShip by Teapplix Demo tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools have clearly distinct purposes (orders, labels, rates, zones, profiles). A few name pairs like manage_tag vs manage_order_tags and set_order_ship_options vs update_order could be confused, but the descriptions explicitly clarify when to use each.

Naming Consistency5/5

All tools share the teapplix_ prefix and follow a consistent verb_noun pattern (e.g., get_orders, create_order, purchase_label, validate_address). The only deviation is the bare 'help' tool, which is conventional and does not disrupt the pattern.

Tool Count4/5

At 28 tools, the server is slightly over the ideal 3-15 range, but the breadth of shipping operations (orders, labels, rates, manifests, tracking, configuration) justifies the count. It is not bloated.

Completeness5/5

The tool surface covers the full order-to-shipping lifecycle: order create/update/retrieve, splitting/merging, label purchase and cancellation, rate quotes, tracking, manifesting, address validation, 3PL submission, and configuration (profiles, warehouses, queues, tags). No significant gaps are apparent.

Resources

Need Help?