Skip to main content
Glama
PocketDraft MCP

PocketDraft MCP

Official
by iPocket-APP

pocketdraft_attach_file

Destructive

Attach a local screenshot, image, or background from the workspace to a PocketDraft project, then commit the update to the paired editor.

Instructions

Attach a local screenshot/image/background within --workspace. Changes are committed to the paired editor.

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": {
      "projectId": "<projectId>",
      "revision": "<revision>",
      "file": "<file>",
      "target": "<target>"
    },
    "name": "pocketdraft_attach_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
targetYes
layerIdNo
canvasIdNo
revisionYes
projectIdYes
cropPolicyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds one useful behavioral fact beyond them – that changes are committed to the paired editor – but never says what the destructive attach overwrites (existing layer/canvas content, interaction with cropPolicy) or what auth/state is required.

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?

Two short sentences, front-loaded with the action and target, with no filler. The odd '--workspace' fragment is the only structural blemish.

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?

An output schema exists, so return values need not be described, but for a 7-parameter destructive mutation with 0% schema coverage the description is far too thin. It omits what cropPolicy reset/preserve does, what layerId/canvasId select, and what revision's 64-hex hash is for.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 7 parameters, and the description only echoes the three 'target' enum values while leaving file, projectId, revision, layerId, canvasId and cropPolicy entirely unexplained in both schema and prose. The stray '--workspace' token does not map to any documented parameter, so it cannot compensate for the coverage gap.

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 gives a specific verb ('Attach') and resource ('local screenshot/image/background'), and names the destination ('within --workspace ... paired editor'). It is clearly distinguishable from siblings like pocketdraft_batch_mutation or pocketdraft_export, though it never explicitly contrasts itself with them.

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 statement of when to use this tool versus alternatives (e.g. batch_mutation, preview), nor any prerequisites such as whether the project must be open in the paired editor first. Usage is only loosely implied by 'within --workspace'.

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