APICK

서식 묶음 ZIP

form_bundle

Read-only

Generate up to 10 Korean forms in one call and return a single ZIP with the documents and an index file. 서식 여러 건을 한 번에 만들어 ZIP 하나로 받습니다. forms 배열의 각 항목은 form_document 와 같은 입력(form·text·data·format·signature_image·stamp_image)을 쓰며, 성공한 건만 합계 과금하고 실패 사유는 ZIP 안 _index.txt 에 남깁니다. [호출당 100포인트]

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": {
      "forms": "<forms>"
    },
    "name": "form_bundle"
  }
}

Input Schema

Name	Required	Description	Default
`forms`	Yes	최대 10건. 각 항목은 {form, text, data, format, signature_image, stamp_image}

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedNov 3, 2026

addedInput schema / properties / forms / items / additionalProperties
```
Added value: +{}
```

addedInput schema / properties / forms / items / properties

Added value: +{
+  "data": {
+    "additionalProperties": {},
+    "description": "정형 필드. 같은 키는 text 보다 우선합니다",
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "form": {
+    "description": "서식 키. 전체 목록은 form_list(무료)",
+    "type": "string"
+  },
+  "format": {
+    "description": "결과 형식, 기본 pdf",
+    "enum": [
+      "pdf",
+      "docx",
+      "hwpx",
+      "rtf",
+      "html",
+      "md",
+      "txt",
+      "json",
+      "xlsx"
+    ],
+    "type": "string"
+  },
+  "text": {
+    "description": "자유 문장",
+    "maxLength": 5000,
+    "type": "string"
+  }
+}

addedInput schema / properties / forms / items / required
```
Added value: +[
+  "form"
+]
```
addedInput schema / properties / forms / items / type
```
Added value: +"object"
```

removedInput schema / properties / forms[].form

Removed value: -{
-  "description": "서식 키. 전체 목록은 form_list(무료)",
-  "type": "string"
-}

removedInput schema / properties / forms[].format

Removed value: -{
-  "description": "결과 형식, 기본 pdf",
-  "enum": [
-    "pdf",
-    "docx",
-    "hwpx",
-    "rtf",
-    "html",
-    "md",
-    "txt",
-    "json",
-    "xlsx"
-  ],
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "forms",
-  "forms[].form"
-]New value: +[
+  "forms"
+]

AddedNov 3, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint=false, so the description carries most of the behavioral load and does so well: partial-failure semantics (only successful items are billed), failure reasons written to _index.txt inside the ZIP, and a cost of 100 points per call. It does not explain whether the ZIP is returned inline or by URL, which is the one remaining gap.

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?

The key facts (batch cap, ZIP output, billing, failure handling) are front-loaded, and the cost indicator is bracketed at the end. The Korean sentence largely mirrors the English one, which is mild redundancy rather than bloat.

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?

For a one-parameter batch tool with no output schema, the description covers the output artifact, per-item input contract, size limit, billing model, and failure reporting. An agent has everything needed to invoke it and interpret the result.

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 already 100%, so the baseline is 3, and the description adds genuine value on top: it enumerates signature_image and stamp_image, which are not listed in the schema's properties, and ties each array item's shape back to form_document's inputs. The data-over-text precedence is only in the schema, not repeated here.

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?

States a specific verb and resource ('Generate up to 10 Korean forms in one call') plus the concrete output ('a single ZIP with the documents and an index file'). It also positions itself against the sibling form_document by name, so an agent can distinguish batch generation from single-document generation without opening either schema.

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 batch limit of 10 and the per-item input shape inherited from form_document clearly imply when this tool is appropriate versus repeatedly calling form_document. There is no explicit 'do not use for a single form' exclusion, but the guidance is clear enough to route correctly.

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

All APICK tools Inspect

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.