Skip to main content
Glama

오늘

today
Read-only

그날 트렌드 지면에 실린 것. 깃허브(github): 머리기사, 7일 동안 별이 가장 많이 늘어난 저장소 10개, 처음 트렌딩에 오른 저장소(since 날짜 이후 처음), 깃허브 일간 트렌딩 목록(rank_day_before가 비면 전날 목록에 없던 저장소, first_trending은 since 날짜 이후 처음 오른 저장소). 쇼핑(commerce): 일주일 사이 분야 10위 안으로 오른 검색어와 작년 이맘때 줄(last_year — times: 검색량이 작년 이맘때의 N배, new: 작년 이맘때엔 거의 찾지 않던 말, holiday: 그 명절마다 오르는 말), 그 아래 함께 본 사실 한 줄(clue — 명절까지 남은 날 · 지난 3년 같은 철 · 같은 분야에서 함께 오른 말, 원인이나 예측이 아닙니다), 분야마다 많이 찾은 검색어 다섯, 분야 100위 안에 새로 든 검색어(since 날짜 이후 새로). since는 트렌드가 그 세계를 기록하기 시작한 날입니다 — 사람에게 전할 때는 지면처럼 그 날이 무엇인지 함께 말해 주세요("트렌드가 기록을 시작한 {since} 이후 처음"). 깃허브의 머리기사(lead의 headline · dek)와 저장소의 kind · summary 가운데 AI가 미리 써 둔 것은 lead와 저장소마다의 ai_written이 적습니다(카드가 없는 저장소의 kind는 저장소가 깃허브에 적은 설명입니다). The day's page on trend.ondo.sh as it prints it: GitHub trending, or what Korean shoppers searched; since is the day trend began recording that world; only the fields listed in ai_written were written by AI. 이용 조건 · Terms of use: https://trend.ondo.sh/about/terms/

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD. 없으면 가장 최근 날
worldYesgithub = 깃허브 트렌딩, commerce = 쇼핑 검색어

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context: what 'since' means, that only fields in ai_written were AI-authored, and that kind falls back to the repo description. It does not discuss freshness limits or response shape, so a 3 is appropriate.

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

Conciseness2/5

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

The description is extremely long and dense, with substantial Korean/English redundancy and field-by-field detail that overlaps the output schema. It is not front-loaded – the core purpose is buried inside enumerations of headline/rank/commerce fields. Several sentences do not earn their place against structured fields that already exist.

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?

An output schema exists, so return values need not be spelled out, yet the description spends most of its length re-describing them while omitting sibling routing and call-time context. For a two-world page tool it is broadly sufficient, but the imbalance leaves real gaps.

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% and both parameters (date, world enum) are documented in the schema itself. The description does not add syntax or format detail for the parameters beyond restating the two worlds; it spends its parameter-adjacent words explaining return fields and the 'since' concept. Baseline 3 is correct.

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

Purpose4/5

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

The description clearly identifies the resource: the day's page on trend.ondo.sh, split between the 'github' (trending repos) and 'commerce' (Korean shopping searches) worlds. The specific verb is implicit ('get/return the day's page') rather than stated, but an agent can infer it. It does not distinguish itself from the sibling tools keyword/repository.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus the sibling keyword or repository tools, and no prerequisites are stated. The only usage hint (date defaults to the most recent day) comes from the schema, not the description. The agent is left to infer selection on its own.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources