get_activities_information
Get detailed information and accurate states of all activities. Provides comprehensive explanations of each activity's current status for monitoring file transfers.
Instructions
Get detailed information about all existing activities and their accurate states description. Always use this tool provide users with detailed explanation about activities and their states.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Implementation Reference
- src/api/activities.ts:108-170 (handler)The actual handler/implementation of the get_activities_information tool. It returns a detailed markdown string describing MASV activities, their types (package_upload_to_masv, package_download_from_masv, link_generation, package_transfer_masv_to_cloud) and their possible states (pending, started, complete, cancelled, error).
function getActivitiesInformation() { const info = ` # MASV Activities ## General Information MASV Activities are records of events that happened with MASV resourses like packages, transfers and links. Activities has states: - pending - started - complete - cancelled - error Activities could transition between states back and forth multiple times. Each activity contains a list of events corresponding to states transitions every time it changes it's state. Usually activities start in "pending" state and finish in either "complete", "cancelled" or "error", but there are exceptions. ## Full list of activities and description of their states ### package_upload_to_masv "package_upload_to_masv" activity is created when new package is created. This can be user uploading package via MASV web app, desktop app or MASV Agent or package can be transferred from connected cloud or on-prem storage integration like AWS S3, Azure or MASV Storage Gateway. - pending - package was created, no files were added yet. - started - first file was added to the package. That usually mean that upload started and is in progress now. - complete - package successfully finalized and is available at MASV. - cancelled - package upload was cancelled. Package was deleted from MASV. - error - error happened during package upload. For additional information see error message attached in "extras" field of activity. Package was deleted from MASV. ### package_download_from_masv "package_download_from_masv" activity is created when user starts downloading MASV package. Note that if package is sent to connected storage integration another activity "package_transfer_masv_to_cloud" is created. - pending and started - once user started downloading first file from the package activity switched to "pending" and then immediately to "started" state. "pending" state on its own doesnt have any meaning and is not used for this activity. - complete - activity transitioned to "complete" state only if user downloaded all of the files from the package and MASV received confirmation from supported clients. If user only downloaded subset of files activity will stay in "started" state. Supported clients that confirm download are: MASV Desktop app, MASV Agent and MASV download with new "zipless" web download page (legacy web download page will not switch activity to "complete" state because we cant get confirmation of that download). - cancelled - this state is never used for this activity. - error - error happened during package download. For additional information see error message attached in "extras" field of the activity. ### link_generation "link_generation" activity is added when new download link is added to the package. - pending - new download link was added to the package. - started - someone opened download link and possibly started downloading the package. - complete - same as for "package_download_from_masv" activity transitioned to "complete" state only if user downloaded all of the files from the package and MASV received confirmation from supported clients. If user only downloaded subset of files activity will stay in "started" state. Supported clients that confirm download are: MASV Desktop app, MASV Agent and MASV download with new "zipless" web download page (legacy web download page will not switch activity to "complete" state because we cant get confirmation of that download). - cancelled - not used for "link_generation" activity. - error - same as for "package_download_from_masv" error happened during package download. For additional information see error message attached in "extras" field of the activity. ### package_transfer_masv_to_cloud "package_transfer_masv_to_cloud" activity is created when package is sent from MASV to connected cloud or on-prem storage integration like AWS S3, Azure or MASV Storage Gateway. - pending - not used for "package_transfer_masv_to_cloud" activity. - started - transfer has started. - complete - transfer has completed. - cancelled - transfer was cancelled. - error - transfer error. For additional information see error message attached in "extras" field of the activity. `; return info; } - src/index.ts:228-243 (registration)The MCP server registration of the tool 'get_activities_information' with a description and an async handler that calls the imported getActivitiesInformation function.
server.registerTool( "get_activities_information", { description: "Get detailed information about all existing activities and their accurate states description. Always use this tool provide users with detailed explanation about activities and their states.", }, async () => { try { const data = getActivitiesInformation(); return mcpOk(data); } catch (error) { return mcpError(error); } }, ); - src/api/activities.ts:80-84 (helper)Supporting usage: getActivitiesInformation() is also called inside getActivities() to attach activity descriptions to the API response data.
const additionalContext = getActivitiesInformation(); data.activities_description = additionalContext; return data; } - src/api/activities.ts:4-59 (schema)The GetActivitiesSchema is the input validation schema for getActivities (the other activity tool). The get_activities_information tool takes no input parameters (no schema needed).
const GetActivitiesSchema = z.object({ page: z .number() .min(1) .describe("Page number of paginated response. First page is 1") .optional(), limit: z .number() .min(1) .max(100) .describe("Number of records returned per page") .optional(), sort: z .string() .describe("Sort results ascending (fieldname) or descending (-fieldname)") .optional(), activity_states: z .array(z.enum(["pending", "started", "complete", "cancelled", "error"])) .describe("Retrieve records that has any of the specified activity states") .optional(), activity_types: z .array( z.enum([ "package_upload_to_masv", "package_download_from_masv", "link_generation", "package_transfer_masv_to_cloud", ]), ) .describe( "Retrieve records that has any of the specified activity types. Activities: package_upload_to_masv - package upload from user or connected storage integration to MASV, package_download_from_masv - user downloading package from MASV, link_generation - adding new download link for the package, package_transfer_masv_to_cloud - package transfer to connected storage integration", ) .optional(), portals: z .array(z.string()) .describe("Retrieve records that belong to any of the specified portal IDs") .optional(), package_id: z .string() .describe("Retrieve records that belongs to the specified package ID") .optional(), created_at_start: z .string() .describe("Retrieve records that were created after (YYYY-MM-DDTHH:mm:SS)") .optional(), created_at_end: z .string() .describe("Retrieve records that were created before (YYYY-MM-DDTHH:mm:SS)") .optional(), teamspaces: z .array(z.string()) .describe( "Retrieve records where teamspace id is equal to one of these values", ) .optional(), });