Skip to main content
Glama
getmasv

masv

Official

send_package_to_integration

Send a MASV package to an integrated cloud or on-prem system like AWS S3, Frame.io, Dropbox, or MASV Storage Gateway. Provide the package ID and integration ID with direction masv_to_cloud.

Instructions

Send MASV package to connected integration. Integration could be cloud or on-prem system like AWS S3, Frame.io, Dropbox, MASV Storage Gateway and many others

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageIdYesId of the package that will be transferred to connected integration
integrationIdYesId of the integration to transfer package to. Integration should have direction: masv_to_cloud.

Implementation Reference

  • The main handler function that sends a package to a connected integration. It constructs a POST request to /v1/packages/{packageId}/transfer with the integration's cloud_connection_id and a package token for authentication.
    async function sendPackageToIntegration({
      packageId,
      integrationId,
    }: SendPackageToIntegrationParams) {
      const url = new URL(`${MASV_BASE_URL}/v1/packages/${packageId}/transfer`);
    
      const packageToken = await getPackageToken(packageId);
    
      const headers = {
        "content-type": "application/json",
        "x-package-token": packageToken,
      };
    
      const body = {
        cloud_connection_id: integrationId,
      };
    
      const r = await fetch(url.toString(), {
        method: "POST",
        headers,
        body: JSON.stringify(body),
      });
      const data = await r.json();
    
      return data;
    }
  • Zod schema defining the input parameters: packageId (string) and integrationId (string).
    const SendPackageToIntegrationSchema = z.object({
      packageId: z
        .string()
        .describe(
          "Id of the package that will be transferred to connected integration",
        ),
      integrationId: z
        .string()
        .describe("Id of the integration to transfer package to. Integration should have direction: masv_to_cloud."),
    });
  • src/index.ts:262-278 (registration)
    Registration of the 'send_package_to_integration' tool with the MCP server, including its description and input schema, along with the callback that invokes the handler.
    server.registerTool(
      "send_package_to_integration",
      {
        description:
          "Send MASV package to connected integration. Integration could be cloud or on-prem system like AWS S3, Frame.io, Dropbox, MASV Storage Gateway and many others",
        inputSchema: SendPackageToIntegrationSchema.shape,
      },
      async (args) => {
        try {
          const data = await sendPackageToIntegration(args);
    
          return mcpOk(data);
        } catch (error) {
          return mcpError(error);
        }
      },
    );
  • TypeScript type inferred from the Zod schema for the sendPackageToIntegration function parameters.
    type SendPackageToIntegrationParams = z.infer<
      typeof SendPackageToIntegrationSchema
    >;
  • Export of the schema and handler for use by the registration site (index.ts).
    SendPackageToIntegrationSchema,
    sendPackageToIntegration,
Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden. It does not disclose whether the operation is synchronous, what happens to the source package, or any side effects. Only a high-level action is described.

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 description is concise at two sentences, front-loading the core action. It is efficient but could be slightly more structured to include key constraints or examples.

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 the lack of output schema, annotations, and the range of possible integrations, the description provides adequate context but misses behavioral details like error conditions or whether the package is moved or copied.

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 input schema has 100% description coverage, so the schema already documents both parameters meaningfully. The description adds no additional semantic value beyond what the schema provides.

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 verb 'Send' and the resource 'MASV package to connected integration', and distinguishes it from sibling tools like get_package or transfer_files_from_integration by specifying the direction and examples of integrations.

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

Usage Guidelines3/5

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

The description does not explicitly state when to use this tool versus alternatives such as transfer_files_from_integration or get_integrations. It implies usage for sending packages to integrations but lacks guidance on 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/getmasv/masv-mcp-server'

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