Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_shipping_profiles

Read-only

List saved local shipping profiles and optionally include full contact or address fields when reviewing them; personal details stay hidden by default.

Instructions

List saved local shipping profiles.

        Args:
            include_addresses: Include full contact/address fields. Defaults
                to ``False`` so listing profiles does not expose personal
                details unless the user is actively reviewing them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_shipping_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_addressesNoInclude full contact/address fields. Defaults to ``False`` so listing profiles does not expose personal details unless the user is actively reviewing them. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • changedInput schema / properties / include_addresses / description
      Previous value: -"Default: false."New value: +"Include full contact/address fields. Defaults to ``False`` so listing profiles does not expose personal details unless the user is actively reviewing them. Default: false."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / include_addresses / default
      Removed value: -false
    • addedInput schema / properties / include_addresses / description
      Added value: +"Default: false."
  3. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context: the default suppresses PII so contact/address data is only exposed deliberately. It says nothing about pagination, ordering, or how many profiles may be returned, so it is additive but not rich.

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 one-line purpose is front-loaded and unambiguous, and the rationale for the default is short. The Args block is redundant with the schema, so a small amount of text does not earn its place, but nothing is padded or verbose.

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 single-parameter read-only list tool with full annotation coverage and no output schema, the definition is serviceable. It still leaves open what a shipping profile contains and whether results are paginated or ordered, which an agent may need when presenting results.

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 description coverage is 100% and the description's Args block reproduces the schema text for include_addresses nearly verbatim, adding no syntax or edge-case detail beyond it. With a single well-documented boolean parameter, the baseline 3 applies.

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 ('List saved local shipping profiles'), and the word 'local' implicitly scopes it away from cloud or remote listings. It does not explicitly name siblings like save_shipping_profile or delete_shipping_profile, but the read-only listing intent is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to call this versus alternatives, and no prerequisites are given. The only usage-adjacent content is the justification for the parameter default ('unless the user is actively reviewing them'), which hints at the review use case but is not a routing rule. An agent must infer everything from the tool name.

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