tw_law_article

Pack: tw-law · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/tw_law_article for the schema, then POST the same URL with its arguments for the data.

One article of a Taiwan law, Chinese plus the official English translation when one exists.

Tool description as the model sees it

Full text of ONE article (條) of a Taiwan law, by pcode or title plus article number in any spelling — “2”, “第 2 條”, “Article 2”, “第 6-1 條”, “Article 6-1”. Returns the Chinese text and, when the Ministry has published an official English translation of that law, the official English text of the SAME article, labelled official (never a machine translation) — plus the chapter/section heading it falls under. A long law is never returned whole; use tw_law_toc to find article numbers, and call this once per article.

Parameters

NameTypeRequiredDescription
pcodestringnoThe law’s pcode (from tw_law_search or tw_law_info).
namestringnoChinese or English law title, used when pcode is not known.
articlestringyesArticle number, any spelling: “2”, “第 2 條”, “Article 2”, “6-1”.

Example call

Arguments

{
  "name": "民法",
  "article": "1"
}

curl

curl -X POST https://gateway.pipeworx.io/tw-law/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"tw_law_article","arguments":{"name":"民法","article":"1"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('tw_law_article', {
  "name": "民法",
  "article": "1"
});

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}
Connect to just the tw-law pack
{
  "mcpServers": {
    "tw-law": {
      "url": "https://gateway.pipeworx.io/tw-law/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build October 16, 2026