Skip to main content
Glama

get_jaish_tsutatsu

Retrieve full-text administrative circulars from Japan's Industrial Safety and Health Information Center (JAISH) for accurate labor law compliance and reference.

Instructions

安全衛生情報センター(JAISH)の通達本文を取得する。search_jaish_tsutatsu で取得した url を指定。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes通達ページのURL(パスまたは完全URL)。search_jaish_tsutatsu の検索結果から取得。例: "/anzen/hor/hombun/hor1-67/hor1-67-1-1-0.htm"

Implementation Reference

  • Tool registration and MCP handler for 'get_jaish_tsutatsu'. It calls the underlying service function to fetch document content.
    export function registerGetJaishTsutatsuTool(server: McpServer) {
      server.tool(
        'get_jaish_tsutatsu',
        '安全衛生情報センター(JAISH)の通達本文を取得する。search_jaish_tsutatsu で取得した url を指定。',
        {
          url: z.string().describe(
            '通達ページのURL(パスまたは完全URL)。search_jaish_tsutatsu の検索結果から取得。例: "/anzen/hor/hombun/hor1-67/hor1-67-1-1-0.htm"'
          ),
        },
        async (args) => {
          try {
            const result = await getJaishTsutatsu({ url: args.url });
    
            const title = result.title || '(タイトル取得不可)';
    
            return {
              content: [{
                type: 'text' as const,
                text: `# ${title}\n\n${result.body}\n\n---\n出典:安全衛生情報センター(中央労働災害防止協会)\nURL: ${result.url}`,
              }],
            };
          } catch (error) {
            return {
              content: [{
                type: 'text' as const,
                text: `エラー: ${error instanceof Error ? error.message : String(error)}`,
              }],
              isError: true,
            };
          }
        }
      );
  • Business logic service function 'getJaishTsutatsu' that fetches and parses the content of a JAISH notice page.
    export async function getJaishTsutatsu(opts: {
      url: string;
    }): Promise<JaishDocument> {
      const html = await fetchJaishPage(opts.url);
      const { title, body } = parseJaishDocument(html);
      const fullUrl = getJaishUrl(opts.url);
    
      return { title, body, url: fullUrl };
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what the tool does (retrieve text) and the input requirement. It doesn't describe what happens on failure, rate limits, authentication needs, response format, or whether it's a read-only operation. The description is minimal and lacks important behavioral context.

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 - just two sentences that directly state the purpose and usage requirement. Every word earns its place with zero waste or redundancy. It's front-loaded with the core purpose followed by implementation guidance.

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 tool with no annotations and no output schema, the description is incomplete. It doesn't explain what format the text returns in (HTML, plain text, structured data), error conditions, or any behavioral characteristics. While the single parameter is well-documented in the schema, the overall context for using this tool effectively is insufficient.

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?

Schema description coverage is 100%, so the schema already fully documents the single 'url' parameter. The description adds marginal value by reinforcing that URLs should come from 'search_jaish_tsutatsu' and specifying it's for '通達本文' (notification text), but doesn't provide additional semantic context beyond what's in the schema. Baseline 3 is appropriate when 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's purpose: '安全衛生情報センター(JAISH)の通達本文を取得する' (retrieve the full text of JAISH notifications). It specifies the resource (JAISH notifications) and the action (retrieve text), but doesn't explicitly differentiate from sibling tools like get_law or get_mhlw_tsutatsu beyond mentioning JAISH specifically.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool: 'search_jaish_tsutatsu で取得した url を指定' (specify the URL obtained from search_jaish_tsutatsu). This establishes a workflow dependency, but doesn't explicitly state when NOT to use it or mention alternatives like get_mhlw_tsutatsu for different notification sources.

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