Skip to main content
Glama
getmasv

masv

Official

get_package_transfers

Retrieve all transfers of a package to storage, including deliveries to cloud or on-premise destinations via MASV.

Instructions

Get all transfers of a package to storage. Transfer is a package delivery via MASV to cloud or on-premise (via MASV Storage Gateway) destination

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageIdYesId of the package to retrieve transfers for. Transfer is a package delivery via MASV to cloud or on-premise (via MASV Storage Gateway) destination

Implementation Reference

  • Handler function that fetches all transfers for a given package by calling MASV API endpoint /v1/packages/{packageId}/transfer
    async function getPackageTransfers({ packageId }: GetPackageTransfersParams) {
      const packageToken = await getPackageToken(packageId);
    
      const url = new URL(`${MASV_BASE_URL}/v1/packages/${packageId}/transfer`);
    
      const headers = {
        "content-type": "application/json",
        "x-package-token": packageToken,
      };
    
      const r = await fetch(url.toString(), { headers });
      const data = await r.json();
    
      return data;
    }
  • Zod schema defining the input for getPackageTransfers (requires packageId string)
    const GetPackageTransfersSchema = z.object({
      packageId: z
        .string()
        .describe(
          "Id of the package to retrieve transfers for. Transfer is a package delivery via MASV to cloud or on-premise (via MASV Storage Gateway) destination",
        ),
    });
  • src/index.ts:138-154 (registration)
    MCP server registration of the 'get_package_transfers' tool with description and input schema
    server.registerTool(
      "get_package_transfers",
      {
        description:
          "Get all transfers of a package to storage. Transfer is a package delivery via MASV to cloud or on-premise (via MASV Storage Gateway) destination",
        inputSchema: GetPackageTransfersSchema.shape,
      },
      async (args) => {
        try {
          const data = await getPackageTransfers(args);
    
          return mcpOk(data);
        } catch (error) {
          return mcpError(error);
        }
      },
    );
  • Helper function that retrieves an access token for a package, used by getPackageTransfers to authenticate the API call
    async function getPackageToken(packageId: string) {
      const data = await getPackage({ packageId });
      return data.access_token;
    }
Behavior3/5

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

With no annotations, the description explains the concept of a transfer but does not disclose behavioral traits such as idempotency, result ordering, pagination, or any side effects. It minimally conveys read-only intent.

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 one sentence that front-loads the action and includes a concise definition. Every word contributes value with no redundancy.

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 simple one-parameter tool with no output schema, the description adequately defines the purpose and resource. However, it lacks usage guidance and behavioral details, leaving minor gaps.

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 coverage is 100% with a single parameter packageId whose description repeats the tool's description. The tool description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 (Get) and resource (transfers of a package) and defines what a transfer is (MASV delivery to cloud or on-premise destination). This distinguishes it from siblings like get_package_files or get_activities.

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?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites, limitations, or exclusions. It lacks explicit usage context.

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/getmasv/masv-mcp-server'

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