Skip to main content
Glama
kyusik-yang

open-assembly-mcp

by kyusik-yang

search_petitions

Search Korean National Assembly petitions by assembly, keyword, and status. Retrieve petition metadata including title, proposer, committee, and current status for pending or closed petitions.

Instructions

국회 청원 목록을 조회합니다.

Query petition records from the National Assembly: pending petitions (계류 청원) or all petitions including closed ones (접수 목록).

Petitions (청원) are formal citizen requests submitted through National Assembly members. This tool returns petition metadata — title, proposer, assembly, committee, status.

Note: Full petition text is not available through the Open API. This tool returns petition records/status, not the content of individual petitions. For research on citizen engagement and petition outcomes, the status and committee routing data returned here is typically sufficient.

Parameter names are based on the API pattern and hollobit/assembly-api-mcp source. If keyword filtering does not return expected results, use query_assembly directly: discover_apis(keyword="청원") → query_assembly(endpoint_code="PTTRCP", params={...})

Args: assembly: 대수 — 필수 (예: "22") keyword: 청원 제목 키워드 (선택, 예: "교육", "환경") include_closed: True이면 처리 완료 청원까지 포함 (PTTRCP 엔드포인트 사용). False이면 계류 중인 청원만 반환 (기본값, nvqbafvaajdiqhehi 사용). page: 페이지 번호 (기본값: 1) page_size: 페이지당 결과수 (기본값: 10)

Returns: petitions: 청원 목록 endpoint_used: 실제 호출된 엔드포인트 코드 count: 이번 페이지 반환 건수 total_count: 전체 건수 has_more: True이면 page+1로 재호출 raw_response: 비표준 응답 형식일 때 전체 JSON

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
keywordNo
assemblyYes
page_sizeNo
include_closedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Discloses that the tool returns only metadata, not full text, and explains the API endpoints behind include_closed. Without annotations, it covers key behavioral traits, though auth or rate limits aren't mentioned.

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?

Well-structured with Korean lead, English explanation, Args, and Returns sections. Slightly verbose but information-dense; every sentence adds value. Minor redundancy in repeating '청원' but acceptable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 5 parameters with 0% schema coverage and an output schema, the description comprehensively covers inputs, outputs, and limitations. It also includes troubleshooting guidance, making it fully self-contained.

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

Parameters5/5

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

Schema has 0% coverage, but the description provides detailed explanations for all 5 parameters, including examples, defaults, and functional behavior (e.g., include_closed switches endpoints). This fully compensates for the schema gap.

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

Purpose5/5

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

Description clearly states it queries petition records from the National Assembly, distinguishes between pending and closed petitions, and specifies what metadata it returns. It also contrasts with query_assembly and addresses limitations, effectively differentiating it from siblings.

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

Usage Guidelines5/5

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

Explicitly states when to use this tool (for petition metadata) and provides an alternative path (discover_apis → query_assembly) if keyword filtering fails. Also notes that full text is unavailable, setting expectations clearly.

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/kyusik-yang/open-assembly-mcp'

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