Skip to main content
Glama

This Weekend (이번 주말)

수집 범위

get_event_coverage
Read-onlyIdempotent

[이번 주말: 축제·공연·전시 찾기] 지금 담긴 행사 자료의 날짜 범위와 마지막 수집 시각을 알려 줍니다. 검색 결과가 비었을 때 먼저 확인하세요.

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": "get_event_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
coverageYes모아 둔 자료의 날짜 범위와 마지막 수집 시각. stale이 true면 저장소 대신 예비 사본에서 읽은 자료입니다.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish the safe read-only, idempotent, closed-world profile, and the description adds genuine operational context: what the response conveys (date range plus last collection time). It doesn't discuss staleness thresholds or how coverage is scoped, but with annotations and an output schema carrying the rest, this is solid.

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?

Two sentences, both earning their place, with the usage condition placed after the what-it-does statement. The bracketed scenario tag '[이번 주말: 축제·공연·전시 찾기]' is mild framing clutter but does orient the reader quickly, so it stays efficient overall.

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?

With zero parameters, rich annotations, and an output schema, the description only needs to explain purpose and trigger, which it does. Minor gap: it doesn't clarify whether 'last collection time' should be used to judge data freshness in absolute terms, but nothing essential is missing to call the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4: no syntax or argument semantics need explaining. The description correctly implies a global, unfiltered query rather than one scoped to a prior search.

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 opens with a specific verb+resource: it reports the date range of the currently loaded event data and the last collection timestamp. It is distinguishable from search_events because it returns coverage metadata rather than event records. It stops short of explicitly naming the sibling it complements, so a 4 rather than a 5.

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?

It gives a clear triggering condition: '검색 결과가 비었을 때 먼저 확인하세요' (when search results are empty, check this first), which routes the agent usefully. There are no explicit when-not conditions or named alternatives (search_events is only implied), so it falls short of full 5 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