Skip to main content
Glama
getmasv

masv

Official

get_package

Retrieve a package by its unique ID to access its details and current status.

Instructions

Get package by id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageIdYesId of the package to retrieve

Implementation Reference

  • src/index.ts:86-101 (registration)
    Registration of the 'get_package' tool on the MCP server. Maps the tool name to the handler function 'getPackage' and schema 'GetPackageSchema'.
    server.registerTool(
      "get_package",
      {
        description: "Get package by id",
        inputSchema: GetPackageSchema.shape,
      },
      async (args) => {
        try {
          const data = await getPackage(args);
    
          return mcpOk(data);
        } catch (error) {
          return mcpError(error);
        }
      },
    );
  • Zod schema for the 'get_package' tool input validation. Defines a required 'packageId' string parameter describing the ID of the package to retrieve.
    const GetPackageSchema = z.object({
      packageId: z.string().describe("Id of the package to retrieve"),
    });
  • Handler function for 'get_package'. Makes a GET request to MASV API v1.1 teams/{teamId}/packages/{packageId} and returns the package data.
    async function getPackage({ packageId }: GetPackageParams) {
      const url = new URL(
        `${MASV_BASE_URL}/v1.1/teams/${MASV_TEAM_ID}/packages/${packageId}`,
      );
    
      const headers = {
        "content-type": "application/json",
        "x-api-key": MASV_API_KEY,
      };
    
      const r = await fetch(url.toString(), { headers });
      const data = await r.json();
    
      return data;
    }
  • Exports including GetPackageSchema and getPackage function used by the tool registration and handler.
    export {
      GetPackagesSchema,
      getPackages,
      GetPackageSchema,
      getPackage,
      GetPortalPackagesSchema,
      getPortalPackages,
      GetPackageFilesSchema,
      getPackageFiles,
      GetPackageTransfersSchema,
      getPackageTransfers,
      UpdatePackageExpiryDateSchema,
      updatePackageExpiry,
      DeletePackageSchema,
      deletePackage,
      getPackageToken,
    };
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits beyond the basic retrieval. There is no mention of what happens if the package ID is invalid, auth requirements, or any side effects. The description is too minimal for a getter.

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, using only the necessary words to convey the action. No superfluous information is present.

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?

Given the tool's simplicity (single required parameter, no output schema), the description is mostly complete. However, it could mention the return value format or error conditions to be fully self-contained.

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 with the 'packageId' parameter described as 'Id of the package to retrieve'. The description adds no additional meaning beyond the schema, meeting the baseline of 3.

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?

Description clearly states 'Get package by id', indicating the verb and resource. However, it does not differentiate from sibling tools like 'get_packages' which retrieves multiple packages. The purpose is clear but lacks distinction.

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. With siblings like 'get_packages' and 'get_package_files', the description should mention that this is for retrieving a single package by ID, leaving no room for confusion.

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