Skip to main content
Glama
yonghwan86

narajangteo-searcher

by yonghwan86

find_deadline_urgent_bids

Find Korean public IT procurement bids with urgent deadlines (within N hours, default 72), sorted by remaining time. Adjust keywords and business type as needed.

Instructions

[마감임박] 마감이 N시간 이내(기본 72h)인 IT 공고를 남은 시간 가까운 순으로 정리. 급히 확인할 조건 포함.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
withinHoursNo마감까지 N시간 이내 (기본 72)
keywordsNoIT 키워드 (미지정 시 기본 세트)
maxResultsNo최대 결과 수 (기본 20)
businessTypeNo업무구분 (기본 용역, '전체'는 5개 업무 통합)용역
openInBrowserNo결과를 별도 브라우저 창(정렬·필터 가능한 HTML 표)으로 띄울지 여부
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses sorting behavior and inclusion of urgent conditions, but does not specify read-only nature, authentication needs, or side effects. Acceptable but incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence that is concise and front-loaded with the category '[마감임박]'. Every word serves a purpose without waste.

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

Completeness2/5

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

The description lacks information on output format and the effect of the 'openInBrowser' parameter. With no output schema, it should at least indicate default result presentation. This gap reduces completeness for a tool with 5 parameters.

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?

Schema coverage is 100%, so baseline is 3. The tool description does not add extra meaning beyond the parameter descriptions in the schema. No additional parameter context is provided.

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 specifies the tool finds IT notices with deadlines within N hours (default 72h) and sorts them by remaining time. The term '마감임박' and '급히 확인할 조건 포함' clearly distinguish it from siblings like search_it_bids and recommend_bids_for_small_it_company.

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 urgent bids by stating '마감임박' and sorting by time proximity. It provides context but does not explicitly state when to use alternatives or when not to use this tool. Clear context but no exclusions.

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/yonghwan86/narajangteo-searcher'

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