Skip to main content
Glama

list_shipping_services

Get a list of available shipping services for your company. Use this to view shipping options in subscription billing.

Instructions

List shipping services. GET /shipping/services. Returns available shipping services for the company.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the list_shipping_services tool logic. It calls shippingService.listShippingServices(client) wrapped in handleToolCall for error handling.
    async function handler(client: Client, _args: Record<string, unknown> | undefined) {
      return handleToolCall(() => shippingService.listShippingServices(client));
  • The tool definition/schema for 'list_shipping_services': name, description, and empty inputSchema (no parameters required).
    const definition = {
      name: "list_shipping_services",
      description: "List shipping services. GET /shipping/services. Returns available shipping services for the company.",
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    };
  • Registration function that returns an array of all shipping tools, including listShippingServicesTool.
    /** All 2 shipping tools. */
    export function registerShippingTools(): Tool[] {
      return [listShippingServicesTool, calculateShippingTool];
    }
  • The handleToolCall helper that wraps the actual API call, catches errors, and formats success/error ToolResult responses.
    export async function handleToolCall<T>(fn: () => Promise<T>): Promise<ToolResult> {
      try {
        const data = await fn();
        return successResult(data);
      } catch (err) {
        const message = err instanceof Error ? err.message : String(err);
        return errorResult(`Error: ${message}`);
      }
    }
  • The actual API service function that makes a GET request to /shipping/services using the client.
    /** GET /shipping/services */
    export async function listShippingServices(client: Client): Promise<unknown> {
      return client.get<unknown>("/shipping/services");
    }
Behavior2/5

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

No annotations are present, so the description bears full responsibility. It states the tool lists and returns shipping services, but does not disclose any behavioral traits such as read-only nature, side effects, or rate limits.

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 extremely concise with two sentences. It front-loads the purpose and adds the HTTP endpoint, all without superfluous information.

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?

Given no output schema, the description could be more complete by describing the return structure or fields. It merely says 'returns available shipping services,' which is adequate but vague. It lacks contextual details about what constitutes a shipping service.

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?

The tool has no parameters, and the input schema coverage is 100% trivially. The description confirms a parameterless operation, which is sufficient. Baseline for 0 parameters is 4.

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 identifies the tool as listing shipping services, includes the HTTP method and path, and specifies it returns available shipping services for the company. It distinguishes itself from sibling list tools by focusing on shipping services.

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?

No guidance is provided on when to use this tool versus alternatives. For example, the sibling 'calculate_shipping' exists but no distinction is made. There is no mention of prerequisites or exclusions.

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/rhinosaas/rebillia-mcp-server'

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