@alog-world/mcp

upload_image

Upload images for article inserts or cover images by providing Base64-encoded data and a filename.

Instructions

画像をアップロード（記事の挿入画像やカバー画像）。Base64データを送信

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": {
      "image": "<image>",
      "filename": "<filename>"
    },
    "name": "upload_image"
  }
}

Input Schema

Name	Required	Description	Default
`image`	Yes	画像のBase64エンコードデータ
`filename`	Yes	ファイル名（例: cover.jpg）

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2May 29, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must cover behavioral traits. It mentions Base64 data upload but omits details like authentication needs, file size limits, supported formats, or what the response contains. The mutation aspect is clear, but safety and side effects are unaddressed.

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 a single, front-loaded sentence with no redundant words. It efficiently conveys the tool's purpose and data format.

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

Completeness2/5

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

Given the lack of output schema and no annotations, the description should explain return values, error conditions, or side effects. It does not, leaving the agent with incomplete information for a simple upload tool.

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 coverage is 100%, so the schema already documents both parameters. The description restates that 'image' is Base64 encoded and gives an example for 'filename', adding minimal value beyond the schema.

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 specifies the action ('upload image') and the context ('for article insertion or cover image'), distinguishing it from sibling tools like 'create_article' or 'bookmark_article'.

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 description implies the tool is for uploading images for articles, but lacks explicit guidance on when to use it over alternatives or any prerequisites. No exclusions are stated.

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