Skip to main content
Glama

everyone-builder

today_digest

오늘 한국 IT 업계에 무슨 일이 있었는지 한국어로 정리한 글을 돌려줍니다. 우리가 모은 자료의 집계를 근거로 쓴 글이라 전문을 제공합니다. 오늘 글이 아직 없으면 어제 것을 주고 isToday: false 로 밝힙니다 — 그때는 날짜를 그대로 전해 주세요.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "today_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does disclose meaningful behavior: the response is a full-text article derived from aggregated collected data (자료의 집계를 근거로 쓴 글이라 전문을 제공합니다), and stale content is surfaced via an isToday: false marker with yesterday's article. That freshness/fallback disclosure is exactly the kind of non-obvious trait an agent needs. It omits caching, refresh cadence, and whether the digest can ever be empty.

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?

Three short sentences, front-loaded with what the tool returns and followed by the fallback condition, with no filler. The trailing clause about passing the date along is the only part that does not clearly earn its place.

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?

There is no output schema, so the description must partially describe the return value; it names the full-text article and the isToday flag but says nothing about other response fields such as title, date, or source list. The fallback semantics are well covered. For a zero-parameter, zero-annotation tool it is adequate but not fully self-contained.

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 schema has zero parameters, so the baseline is 4, but the final clause ('in that case, pass the date as-is' – 그때는 날짜를 그대로 전해 주세요) tells the caller to relay a date when there is no date input to supply, which adds confusion rather than meaning. Nothing in the description clarifies the date field carried in the response. This ambiguity pulls the score below baseline.

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?

A concrete verb and resource are stated: it 'returns a Korean-language write-up of what happened in the Korean IT industry today' (한국 IT 업계에 무슨 일이 있었는지 한국어로 정리한 글), which is clearly a daily digest article rather than a raw news feed like the sibling korea_it_news. The scope (today, Korean IT, Korean language) is specific. It stops short of naming a sibling to distinguish itself from, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

Usage is only implied: the description establishes that this is the daily-summary surface, but never says when to prefer it over korea_it_news or media_comparison. The one explicit conditional is a fallback rule ('if today's article isn't there yet, it gives yesterday's' – 오늘 글이 아직 없으면 어제 것을 주고), which is behavior, not tool selection guidance.

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