Skip to main content
Glama

APICK AI

by app.apick
OverviewDiscussionsAdmin

이미지 대량 작업 생성

image_batch_create

이미지 1~50장의 비동기 생성 또는 편집 작업을 접수합니다. 요금은 품질별 장당 고정가(기본 40P·고급 350P·최고급 1,400P)이며 장수만큼 선차감하고 실패한 장은 환급합니다. 같은 요청도 매번 새 작업으로 접수하며, 접수 후에는 취소할 수 없습니다. [장당 기본 40P · 고급 350P · 최고급 1,400P]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYes작업 방식
sizeNo표준 출력 크기, 기본 1024x1024
promptYes생성 또는 편집 지시, 최대 28,000자
qualityNo이미지 품질. basic(기본) 40P, advanced(고급) 350P, premium(최고급) 1,400P(장당). 기본 basic
image_urlNo편집 모드에서 변경할 원본 이미지 URL — 다운로드 가능한 https URL (허용 형식: image/png, image/jpeg, image/webp) (최대 50MB)
backgroundNo배경 방식
image_countYes만들 이미지 장수, 1~50
output_formatNo출력 포맷
reference_image_urlNo생성 모드에서 사용할 참고 이미지 URL — 다운로드 가능한 https URL (허용 형식: image/png, image/jpeg, image/webp) (최대 50MB)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / idempotency_key
      Removed value: -{
-  "description": "같은 요청의 재전송으로 인한 중복 생성·과금을 막는 고유 키",
-  "maxLength": 128,
-  "minLength": 8,
-  "pattern": "^[A-Za-z0-9_-]+$",
-  "type": "string"
-}
    • addedInput schema / properties / quality
      Added value: +{
+  "description": "이미지 품질. basic(기본) 40P, advanced(고급) 350P, premium(최고급) 1,400P(장당). 기본 basic",
+  "enum": [
+    "basic",
+    "advanced",
+    "premium"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: async submission, per-image pricing tiers with upfront deduction and refunds for failures, non-idempotency (same request re-creates a new job), and irreversibility ('접수 후에는 취소할 수 없습니다'). This reinforces idempotentHint=false with concrete detail the annotation can't convey.

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?

Purpose is front-loaded and sentences are tight, but the pricing (basic 40P·advanced 350P·premium 1,400P) is stated twice — once in the body and again in the trailing bracket — which is pure redundancy.

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?

For an async, non-cancelable, paid batch job the description covers cost, refunds, and irreversibility well. The main omission is any pointer to image_batch_status/image_batch_result, which the agent needs to retrieve results, though the async nature implies polling.

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 9 parameters are already documented, including the quality tiers and their prices. The description repeats the same price mapping in prose, adding essentially no new meaning over the schema.

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?

States a specific verb (접수/accept) and resource (비동기 생성·편집 대량 작업 for 1-50 images), so the agent knows this submits bulk async image jobs. It never names the single-image siblings (image_generate, image_edit) it competes with, so differentiation is left to the '대량'/'1~50장' scope only.

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?

The 1-50 image count and '대량' framing imply this is the bulk path versus single-image tools, but there is no explicit when-to-use, when-not-to-use, or named alternative. Usage is inferable from scope rather than stated.

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

All APICK AI 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