Skip to main content
Glama
gitbosung

open-ALIO-mcp

by gitbosung

get_institution_briefing

Retrieve a comprehensive briefing on any Korean public institution, combining profile, key metrics trends, recent news headlines, and current job openings in a single summary.

Instructions

기관 360° 원샷 브리핑 — 프로필·핵심지표 추세·최근 뉴스·진행중 채용을 한 번에 종합합니다.

org_code 또는 query(기관명·별칭, 예 '한전')로 기관을 지정합니다. 프로필(설립목적·기관장·부처) + 정원/보수/부채비율 추세 + 최근 N일 뉴스 헤드라인 + 진행중 채용 건수를 묶어 반환합니다. "○○기관 한눈에 브리핑해줘"에 사용하세요.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
org_codeNo
queryNo
news_daysNo
metric_yearsNo
news_countNo
Behavior3/5

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

The description lists the components returned but does not explicitly state read-only behavior, rate limits, or any side effects. Since annotations are absent, the description should cover safety but falls short.

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?

Description is concise with a clear purpose statement followed by a structured list of returned components. No fluff, but could explicitly parameter mapping.

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

Completeness3/5

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

The description lists return categories and identifies the institution via org_code or query, but fails to explain parameter defaults, behavior when both identifiers are missing, or the format of metrics trends. With no output schema and no annotations, more detail is needed.

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?

The description explains the use of org_code and query, and hints at news recency and count, but does not explicitly map to all five parameters (e.g., metric_years is omitted). With 0% schema coverage, the description should document all parameters.

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 it aggregates profile, key metric trends, recent news, and recruitment into a one-shot briefing, and distinguishes it from sibling tools that provide individual pieces of information. Example usage is provided.

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 implies usage for a comprehensive overview, but does not explicitly contrast with siblings or provide when-not-to-use scenarios.

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/gitbosung/open-ALIO-mcp'

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