Skip to main content
Glama
kyusik-yang

open-assembly-mcp

by kyusik-yang

get_schedule

Retrieve the National Assembly schedule including plenary sessions, committee meetings, and public hearings. Filter by assembly term, schedule type, and committee name.

Instructions

국회 일정을 조회합니다 (본회의·위원회·공청회 등).

Query the National Assembly schedule: plenary sessions, committee meetings, public hearings, and other proceedings.

Schedule type determines which endpoint is used:

  • "all" → ALLSCHEDULE (모든 종류 통합, 가장 포괄적)

  • "plenary" → nekcaiymatialqlxr (본회의만)

  • "committee" → nrsldhjpaemrmolla (위원회만, committee 필터 사용 가능)

Note: Parameter names are based on the API pattern. If date filtering or committee filtering does not work as expected, use query_assembly directly.

Args: assembly: 대수 — 필수 (예: "22") schedule_type: 일정 종류 — "all" (기본값) | "plenary" | "committee" committee: 위원회명 필터 (선택, schedule_type="committee"일 때만 적용, 예: "법제사법위원회") page: 페이지 번호 (기본값: 1) page_size: 페이지당 결과수 (기본값: 20)

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
assemblyYes
committeeNo
page_sizeNo
schedule_typeNoall

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, but description discloses endpoint selection logic, committee filter constraint, and raw_response for non-standard formats. It is a read operation and no destructive behavior is implied.

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 sections and bilingual summary, but slightly verbose with redundant translations. Core purpose is front-loaded.

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

Completeness4/5

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

Covers input parameters thoroughly, notes output fields, and provides fallback advice. Without the output schema, we cannot fully assess, but the description seems sufficient.

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% description coverage, but description adds comprehensive explanations for each parameter: assembly is required with example, schedule_type values are listed with mapping to endpoints, committee with example and condition, page and page_size with defaults.

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?

The description clearly states the tool queries the National Assembly schedule, listing specific types (plenary, committee, hearings). It distinguishes from sibling tools like query_assembly by specifying when to use the alternative.

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?

Explicit guidance on when to use this tool vs alternatives: if filtering fails, use query_assembly. Also explains schedule_type determines endpoint usage and committee filter only applies for committee type.

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