trip-planner-mcp

get_day_content

Retrieve the full markdown content for a specific day of a trip to verify original activities before conversion.

Instructions

일자의 전체 마크다운 콘텐츠를 조회한다. 활동 변환 시 원본 확인용.

Args: trip_id: 여행 ID day_id: 일자 ID (get_trip에서 확인)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "trip_id": "<trip_id>",
      "day_id": "<day_id>"
    },
    "name": "get_day_content"
  }
}

Input Schema

Name	Required	Description	Default
`day_id`	Yes
`trip_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 29, 2026

TDQS

A4.3/5.0

Behavior3/5

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

No annotations provided, and the description only states 'retrieves full markdown content'. It does not disclose behavioral traits like read-only nature, error handling, or performance. However, the tool is simple and the description is adequate for a get operation.

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 concise: two sentences and arg definitions, no fluff. It is front-loaded with the main purpose.

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

Completeness5/5

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

The tool has an output schema, so return values are covered. The description is complete for a simple read operation with no missing gaps.

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?

Schema coverage is 0%, but the description adds meaning to both parameters: trip_id is '여행 ID' and day_id is '일자 ID' with a note to confirm via get_trip. This helps beyond the schema's basic type and title.

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 the tool retrieves the full markdown content of a day, with a specific use case (checking original when converting activities). It is distinct from siblings like clear_day_content or update_day.

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 mentions a specific use case ('활동 변환 시 원본 확인용'), giving context for when to use. It does not explicitly exclude other uses or mention alternatives, but the purpose is clear.

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

Deploy Server

Other Tools

get_day_contentA