Skip to main content
Glama
Sign In
labor-law-mcp

labor-law-mcp

by kentaroajisaka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to labor-law-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-japan-law

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying Japanese national laws and ordinances via the e-Gov Law API, allowing AI agents to access legal data through natural language questions.
      623 npm
      MIT

    • jp-law-mcp

      yabooung
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to look up Japanese statutes and articles as of a chosen date, compare old and new versions, full-text search law bodies, and search National Diet session records. It also verifies whether legal citations in a document actually exist and traces which provisions cite or are cited by a given article.
      9
      41 npm
      Apache 2.0

    • law-graph

      NexA-LLC
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search and resolve Japanese legal provisions, inspect related laws and concepts, and traverse source-grounded relationships with explicit coverage and read-only access.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity: three tools are for searching (search_jaish_tsutatsu, search_law, search_mhlw_tsutatsu) and three are for retrieving specific content (get_jaish_tsutatsu, get_law, get_mhlw_tsutatsu), each targeting different data sources (JAISH, laws, MHLW). The separation between search and get functions is explicit, preventing misselection.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout: all tools use 'get_' or 'search_' prefixes followed by the specific noun (e.g., get_law, search_mhlw_tsutatsu). This predictable naming scheme makes it easy for agents to understand and select tools based on their intended actions.

    Tool Count5/5

    The number of tools (6) is well-scoped and appropriate for the server's purpose of accessing Japanese labor law and related documents. Each tool earns its place by covering distinct aspects of the domain (searching and retrieving from different sources), without being too sparse or overwhelming.

    Completeness5/5

    The tool surface is complete for the domain of Japanese labor law access, providing full CRUD-like coverage: search tools for discovering relevant documents and get tools for retrieving specific content, with no obvious gaps. This allows agents to perform end-to-end workflows from search to detailed retrieval without dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessSyncing

    Resources