Skip to main content
Glama
Sign In

APICK Convert

by app.apick
OverviewDiscussionsAdmin

문서·첨부 ZIP 다운로드

document_download_bundle
Idempotent

DOCX와 첨부를 ZIP으로 받습니다. 기존 문서 구매 권리를 사용합니다. 최초 100P, 같은 내용 재다운로드 무료. [최초 100P · 같은 내용 재다운로드 무료]

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": {
      "document_id": "<document_id>",
      "version": "<version>",
      "content_hash": "<content_hash>",
      "request_id": "<request_id>"
    },
    "name": "document_download_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
versionYes마지막으로 읽은 문서 버전
request_idYes중복 방지 요청 ID. UUID 권장, 같은 요청의 재시도는 같은 값
document_idYes내 문서 ID
content_hashYes견적 응답의 내용 해시

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false and idempotentHint=true; the description adds genuinely new context by stating that a first download costs 100P while a re-download of identical content is free, which explains why the tool is marked idempotent and why content_hash exists. What it omits is the return form (a URL or a binary stream) and any size or attachment-count limits.

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

Conciseness3/5

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

The purpose sentence is front-loaded and efficient, but the pricing sentence is repeated verbatim in a bracketed trailer, so one of four lines is pure duplication. Trimming that redundancy would strengthen the definition without losing information.

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?

For a four-required-parameter, paid download tool with no output schema, the description covers the billing angle but leaves gaps: it does not say what the response returns, whether the caller must first obtain a quote or hold existing purchase rights, or what happens when content_hash does not match the stored content.

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 description coverage is 100%, so all four required parameters are already documented in the input schema, and the baseline of 3 applies. The description's note about free re-downloads loosely motivates content_hash, but it never ties that parameter to the pricing rule or explains what version refers to.

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 names a specific verb and resource: receiving a DOCX plus its attachments packaged as a ZIP. That is enough to tell it apart from a plain document fetch, but it never names document_download or document_download_pdf, so the agent must infer the bundle-versus-single-file distinction from the name alone.

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 explicit statement of when to choose this tool over document_download or document_download_pdf, and no prerequisites or exclusions are given. The billing sentence implicitly suggests a repeat-download scenario, but that is inference rather than guidance.

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

All APICK Convert toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources