Skip to main content
Glama

search_mhlw_tsutatsu

Search Japanese labor law administrative circulars from the Ministry of Health, Labour and Welfare database using keywords. Find official notices on employment standards, social insurance, workplace safety, and related regulations.

Instructions

厚生労働省の法令等データベースから通達をキーワード検索する。労働基準、雇用保険、安全衛生、社会保険等の行政通達を検索可能。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYes検索キーワード。例: "36協定", "有給休暇", "労災認定", "社会保険適用拡大", "育児休業給付"
pageNoページ番号(0始まり、デフォルト0)。1ページあたり約20件。

Implementation Reference

  • The handler function that registers the 'search_mhlw_tsutatsu' MCP tool, defines its schema, and executes the search logic.
    export function registerSearchMhlwTsutatsuTool(server: McpServer) {
      server.tool(
        'search_mhlw_tsutatsu',
        '厚生労働省の法令等データベースから通達をキーワード検索する。労働基準、雇用保険、安全衛生、社会保険等の行政通達を検索可能。',
        {
          keyword: z.string().describe(
            '検索キーワード。例: "36協定", "有給休暇", "労災認定", "社会保険適用拡大", "育児休業給付"'
          ),
          page: z.number().optional().describe(
            'ページ番号(0始まり、デフォルト0)。1ページあたり約20件。'
          ),
        },
        async (args) => {
          try {
            const result = await searchMhlwTsutatsu({
              keyword: args.keyword,
              page: args.page,
            });
    
            if (result.results.length === 0) {
              return {
                content: [{
                  type: 'text' as const,
                  text: `「${args.keyword}」に一致する通達が見つかりませんでした。\nキーワードを変えて再検索してください(例: 類義語・上位概念・正式名称を試す)。\n安全衛生関連の場合は search_jaish_tsutatsu も試してください。`,
                }],
              };
            }
    
            const lines = result.results.map((r, i) => {
              const num = (result.page * 20) + i + 1;
              return `${num}. **${r.title}**\n   日付: ${r.date}\n   番号: ${r.shubetsu}\n   data_id: \`${r.dataId}\``;
            });
    
            return {
              content: [{
                type: 'text' as const,
                text: `# 厚労省通達検索結果: 「${args.keyword}」\n\n該当件数: ${result.totalCount}件(${result.page + 1}ページ目)\n\n${lines.join('\n\n')}\n\n---\n※ 本文を読むには get_mhlw_tsutatsu で data_id を指定してください。\n出典:厚生労働省 法令等データベース`,
              }],
            };
          } catch (error) {
            return {
              content: [{
                type: 'text' as const,
                text: `エラー: ${error instanceof Error ? error.message : String(error)}`,
              }],
              isError: true,
            };
          }
        }
      );
    }
  • The core service function that performs the MHLW search by fetching and parsing the HTML content.
    export async function searchMhlwTsutatsu(opts: {
      keyword: string;
      page?: number;
    }): Promise<MhlwSearchResponse> {
      const page = opts.page ?? 0;
      const html = await fetchMhlwSearch(opts.keyword, page);
      const results = parseMhlwSearchResults(html);
      const totalCount = parseMhlwSearchCount(html);
    
      return { results, totalCount, page };
    }
  • src/server.ts:89-89 (registration)
    Registration of the 'search_mhlw_tsutatsu' tool in the main server setup.
    registerSearchMhlwTsutatsuTool(server);  // search_mhlw_tsutatsu: 通達検索
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. While it mentions the search capability and domain areas, it doesn't describe important behavioral aspects like authentication requirements, rate limits, pagination behavior beyond the page parameter, error conditions, or what the search results look like. For a search tool with no annotation coverage, this is a significant gap.

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 appropriately concise with two sentences that efficiently convey the tool's purpose and scope. The first sentence states the core functionality, and the second provides domain context. There's no wasted text, though it could be slightly more structured for clarity.

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?

For a search tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the search returns (formats, structure, fields), doesn't mention authentication or rate limiting, and provides minimal behavioral context. The description should do more to compensate for the lack of structured metadata.

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 schema description coverage is 100%, so the schema already fully documents both parameters (keyword and page). The description doesn't add any parameter-specific information beyond what's in the schema, such as search syntax, keyword matching behavior, or result ordering. Baseline 3 is appropriate when the schema does the heavy lifting.

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 tool searches for administrative notices from the Ministry of Health, Labour and Welfare database using keyword search. It specifies the resource (通達/administrative notices) and verb (検索/search), but doesn't explicitly differentiate from sibling tools like search_jaish_tsutatsu or search_law beyond mentioning the specific ministry scope.

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 mentions the types of administrative notices that can be searched (labor standards, employment insurance, safety and hygiene, social insurance), but provides no guidance on when to use this tool versus the sibling tools like search_jaish_tsutatsu or search_law. There's no explicit when/when-not usage context or alternative tool recommendations.

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/kentaroajisaka/labor-law-mcp'

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