Skip to main content
Glama

get_folder

Retrieve detailed information about a specific folder in Zephyr Scale Cloud test management, including its structure and contents, by providing the folder ID.

Instructions

Get detailed information about a specific folder

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folderIdYesFolder ID to retrieve

Implementation Reference

  • The main handler function for the 'get_folder' tool. Validates the folderId input, fetches the folder using ZephyrClient.getFolder, and returns formatted JSON or error response.
    async function getFolder(args) {
      try {
        const { folderId } = args;
        if (!folderId) {
          throw new Error('folderId is required');
        }
    
        if (!config.folderIdPattern.test(folderId)) {
          throw new Error('Invalid folderId format. Must be a numeric ID.');
        }
    
        const folder = await client.getFolder(folderId);
    
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(folder, null, 2)
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: formatError(error, `fetching folder ${args.folderId}`)
            }
          ],
          isError: true
        };
      }
    }
  • Input schema definition for the 'get_folder' tool, specifying folderId as required string with pattern validation.
    inputSchema: {
      type: 'object',
      properties: {
        folderId: {
          type: 'string',
          description: 'Folder ID to retrieve',
          pattern: config.folderIdPattern.source
        }
      },
      required: ['folderId']
    },
  • Tool registration object defining name 'get_folder', description, inputSchema, and handler reference. Part of the folderTools export array.
    {
      name: 'get_folder',
      description: 'Get detailed information about a specific folder',
      inputSchema: {
        type: 'object',
        properties: {
          folderId: {
            type: 'string',
            description: 'Folder ID to retrieve',
            pattern: config.folderIdPattern.source
          }
        },
        required: ['folderId']
      },
      handler: getFolder
    },
  • src/index.js:30-37 (registration)
    Central registration where folderTools (including 'get_folder') are spread into allTools array used for dynamic tool lookup and execution in MCP server.
    const allTools = [
      ...projectTools,
      ...folderTools,
      ...testCaseTools,
      ...testStepsTools,
      ...testScriptTools,
      ...referenceDataTools
    ];
  • ZephyrClient helper method that makes the API request to retrieve a specific folder by ID.
    async getFolder(folderId) {
      return this.request('GET', `/folders/${folderId}`);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves 'detailed information' but doesn't specify what that includes, whether it's a read-only operation, error handling, or any constraints. This leaves key behavioral traits unclear for a tool that likely involves data retrieval.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'detailed information' entails, potential return values, or error scenarios. For a data retrieval tool with no structured output documentation, this leaves significant gaps in understanding how to use it effectively.

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 description adds minimal meaning beyond the input schema, which has 100% coverage and clearly documents the 'folderId' parameter. The description implies the parameter identifies a 'specific folder' but doesn't provide additional context like format examples or usage notes, meeting the baseline for high schema coverage.

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?

The description clearly states the verb ('Get') and resource ('detailed information about a specific folder'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'list_folders' or other 'get_' tools like 'get_test_case', missing explicit differentiation that would warrant a score of 5.

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. It doesn't mention when to choose 'get_folder' over 'list_folders' for folder information or specify prerequisites like needing a folder ID, which is a significant gap in 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/donyfs/mcp-zephyr'

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