Skip to main content
Glama
tmhr1850

Backlog MCP Server

getSpaces

Retrieve space information from Backlog to access project management data and configure workspace settings for team collaboration.

Instructions

スペース情報の取得

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Generic async handler function executed for the 'getSpaces' tool. Validates parameters against the tool's Zod schema, processes the path ('space'), invokes the Backlog API via fetchFromBacklog, and returns the response as formatted JSON text or error message.
    const handler = async (params: Record<string, unknown>): Promise<McpResponse> => {
      try {
        // パラメータのバリデーション
        const validatedParams = await endpoint.schema.parseAsync(params);
    
        // URL中のプレースホルダーを置換
        let path = endpoint.path;
        
        // URIスキーム(例:space://info)の場合はBacklog APIのパスに変換
        if (path.includes('://')) {
          // URIスキームを取り除いてAPIパスに変換
          const uriParts = path.split('://');
          const resourceType = uriParts[0];
          const resourcePath = uriParts[1];
          
          // リソースタイプに応じてAPIパスを構築
          switch (resourceType) {
            case 'space':
              path = 'space';
              break;
            case 'projects':
              if (resourcePath === 'list') {
                path = 'projects';
              } else {
                path = `projects/${resourcePath}`;
              }
              break;
            case 'issues':
              if (resourcePath.includes('/list')) {
                const projectPart = resourcePath.split('/')[0];
                path = 'issues';
                validatedParams.projectIdOrKey = projectPart;
              } else if (resourcePath.includes('/details')) {
                const issuePart = resourcePath.split('/')[0];
                path = `issues/${issuePart}`;
              }
              break;
            case 'wikis':
              if (resourcePath.includes('/list')) {
                const projectPart = resourcePath.split('/')[0];
                path = 'wikis';
                validatedParams.projectIdOrKey = projectPart;
              }
              break;
            case 'users':
              path = 'users';
              break;
            default:
              path = resourcePath;
          }
        }
        
        // 通常のパスパラメータの置換処理
        for (const [key, value] of Object.entries(validatedParams)) {
          if (typeof value === "string" || typeof value === "number") {
            const placeholder = `{${key}}`;
            if (path.includes(placeholder)) {
              path = path.replace(placeholder, String(value));
              // プレースホルダーとして使用したパラメータは削除
              delete validatedParams[key];
            }
          }
        }
    
        // メソッドの追加
        if (endpoint.method !== "GET") {
          validatedParams.method = endpoint.method;
        }
    
        // APIリクエストの実行
        const data = await fetchFromBacklog(path, validatedParams);
        return {
          content: [{ 
            type: "text" as const, 
            text: JSON.stringify(data, null, 2) 
          }],
        };
      } catch (error: any) {
        // エラーメッセージの整形
        const errorMessage = error.errors 
          ? `バリデーションエラー: ${JSON.stringify(error.errors)}`
          : `エラー: ${error.message}`;
    
        return {
          content: [{ 
            type: "text" as const, 
            text: errorMessage 
          }],
          isError: true,
        };
      }
    };
  • Registration of the 'getSpaces' tool on the MCP server using server.tool(), called within a loop over all defined endpoints. Passes the name, description, and the generic handler.
    if (endpoint.type === "tool") {
      // ツールの登録
      server.tool(
        endpoint.name,
        endpoint.description,
        async (args: Record<string, unknown>) => handler(args)
      );
  • Tool configuration object for 'getSpaces', including empty input schema (z.object({})), description, path ('space'), method ('GET'), and type ('tool'). Used for validation and dispatching.
    {
      name: "getSpaces",
      description: "スペース情報の取得",
      path: "space",
      method: "GET",
      schema: z.object({}),
      type: "tool",
    },
  • Core helper function fetchFromBacklog that performs the actual HTTP request to Backlog API (/api/v2/{endpoint}). Handles authentication via env vars, query/body params, path substitution, comprehensive error handling for Backlog errors, network issues, etc. Called by the tool handler for 'getSpaces' with endpoint='space'.
        const domain = process.env.BACKLOG_DOMAIN?.trim();
        const apiKey = process.env.BACKLOG_API_KEY?.trim();
        
        if (!domain || !apiKey) {
          throw new Error(
            "環境変数BACKLOG_DOMAINまたはBACKLOG_API_KEYが設定されていません"
          );
        }
    
        // パラメータのサニタイズ
        const sanitizedParams = Object.fromEntries(
          Object.entries(params).map(([key, value]) => [
            key,
            typeof value === "string" ? value.trim() : value
          ])
        );
    
        // エンドポイントのパスパラメータを置換
        let processedEndpoint = endpoint;
        if (endpoint.includes("{")) {
          // {issueId}のようなパスパラメータを実際の値で置換
          const matches = endpoint.match(/\{([^}]+)\}/g) || [];
          for (const match of matches) {
            const paramName = match.slice(1, -1); // {issueId} -> issueId
            if (sanitizedParams[paramName]) {
              processedEndpoint = processedEndpoint.replace(
                match,
                sanitizedParams[paramName]
              );
              delete sanitizedParams[paramName]; // URLに埋め込んだパラメータは削除
            } else {
              throw new Error(`パスパラメータ ${paramName} が指定されていません`);
            }
          }
        }
    
        // URLの構築
        const url = new URL(`https://${domain}/api/v2/${processedEndpoint}`);
        url.searchParams.append("apiKey", apiKey);
    
        // メソッドの判定
        const method = sanitizedParams.method || (endpoint.toLowerCase().includes("post") ? "POST" : "GET");
        delete sanitizedParams.method; // methodパラメータは削除
    
        // リクエストオプションの準備
        const options: RequestInit = {
          method,
          headers: {
            "User-Agent": "Backlog-MCP-Server/1.0.0",
            "Accept": "application/json"
          }
        };
    
        // POSTリクエストの場合はボディにパラメータを設定
        if (method === "POST") {
          // POSTリクエストの場合はFormDataを使用(Backlog APIの仕様に合わせる)
          const formData = new URLSearchParams();
          for (const [key, value] of Object.entries(sanitizedParams)) {
            if (value !== undefined && value !== null) {
              // 配列の場合は複数のパラメータとして追加
              if (Array.isArray(value)) {
                value.forEach(item => {
                  formData.append(`${key}[]`, String(item));
                });
              } else {
                formData.append(key, String(value));
              }
            }
          }
          options.body = formData.toString();
          options.headers = {
            ...options.headers,
            "Content-Type": "application/x-www-form-urlencoded"
          };
        } else {
          // GETリクエストの場合はURLにパラメータを追加
          for (const [key, value] of Object.entries(sanitizedParams)) {
            if (value !== undefined && value !== null) {
              // 配列の場合は複数のパラメータとして追加
              if (Array.isArray(value)) {
                value.forEach(item => {
                  url.searchParams.append(`${key}[]`, String(item));
                });
              } else {
                url.searchParams.append(key, String(value));
              }
            }
          }
        }
    
        // デバッグ情報(開発時のみ使用)
        if (process.env.NODE_ENV === 'development') {
          console.log(`[DEBUG] リクエスト: ${method} ${url.toString()}`);
          if (method === 'POST') {
            console.log(`[DEBUG] リクエストボディ: ${options.body}`);
          }
        }
    
        // リクエストの実行
        const response = await fetch(url.toString(), options);
        const data = await response.json();
    
        // Backlogエラーレスポンスのチェックとハンドリング
        if (isBacklogError(data)) {
          const error = data.errors[0];
          const errorDetails = error.moreInfo ? ` (詳細: ${error.moreInfo})` : '';
          throw new Error(`Backlogエラー [${error.code}]: ${error.message}${errorDetails}`);
        }
    
        if (!response.ok) {
          throw new Error(`HTTPエラー ${response.status}: ${response.statusText}`);
        }
    
        return data;
      } catch (error) {
        if (error instanceof Error) {
          // エラーの種類に応じて詳細なメッセージを提供
          if (error.message.includes('ENOTFOUND')) {
            throw new Error(`Backlog API接続エラー: ドメイン ${process.env.BACKLOG_DOMAIN} に接続できません`);
          } else if (error.message.includes('ETIMEDOUT')) {
            throw new Error(`Backlog API接続タイムアウト: リクエストがタイムアウトしました`);
          } else if (error.message.includes('SyntaxError')) {
            throw new Error(`Backlog APIレスポースエラー: 不正なJSONレスポンスを受信しました`);
          } else {
            throw new Error(`Backlog API呼び出しエラー: ${error.message}`);
          }
        }
        throw error;
      }
    } 
  • server.ts:29-29 (registration)
    Invocation of registerEndpoints which registers all tools including 'getSpaces' on the MCP server instance.
    registerEndpoints(server);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states what the tool does ('get space information') without any additional context about permissions, rate limits, what 'space information' includes, or how the data is returned. For a tool with zero annotation coverage, this leaves critical behavioral traits unspecified.

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 a single, efficient phrase ('スペース情報の取得') that directly states the tool's purpose without unnecessary words. It's appropriately sized for a no-parameter tool, though it could be more structured if it included additional context. There's no waste, but it's borderline minimal.

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 for effective use. It doesn't explain what 'space information' entails, how it's formatted, or any dependencies. For a tool with no structured data to supplement it, the description should provide more context about the return values and usage scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, meaning there are no parameters to document. The description doesn't need to add parameter semantics beyond the schema, so it meets the baseline. However, it doesn't explicitly state that no parameters are required, which could be slightly improved for clarity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'スペース情報の取得' (Get space information) states a clear verb ('取得' - get) and resource ('スペース情報' - space information), which meets the basic requirement. However, it doesn't distinguish this tool from its siblings like getProjects or getUsers, which follow similar patterns for different resources. The purpose is clear but lacks sibling differentiation.

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. There are no explicit instructions on when/when-not to use it, nor any mention of prerequisites or context. Given the sibling tools include getProjects and getUsers, which might retrieve related data, the absence of usage guidelines is a significant gap.

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/tmhr1850/backlog-mcp-server'

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