pebble-mcp

Overview Schema Source Related Servers Discussions Admin

project_add_resource

Add images, fonts, or raw files to a Pebble project and register them for packaging. Supports base64 bitmaps and optional design-tier processing for target screens.

Instructions

Add a resource to a project and register it in package.json.

Copies source into <dir>/resources/ (created if missing) and appends/updates a resources.media entry with the given name and resource_type ("bitmap" | "font" | "raw"). For bitmaps, source may also be base64 / a data: URI, and passing prep_target (e.g. "emery", "menu-icon") routes the image through the design tier -- resize/letterbox + palette quantize -- before writing it. Returns the updated media list and the written file.

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": {
      "dir": "<dir>",
      "source": "<source>",
      "name": "<name>"
    },
    "name": "project_add_resource"
  }
}

Input Schema

Name	Required	Default
`dir`	Yes
`name`	Yes
`source`	Yes
`prep_target`	No
`resource_type`	No	bitmap

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries full burden. It discloses key behaviors: copying source, creating directories if missing, appending/updating the media entry, supporting base64/data URIs for bitmaps, routing through the design tier when prep_target is set, and returning the updated media list and written file. This is thorough and transparent.

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 description is efficiently structured, front-loading the primary purpose in the first sentence. Subsequent sentences add necessary detail about copying, registration, and edge cases. It's slightly long but every sentence contributes valuable information, so it's appropriately concise.

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 tool with 5 parameters, no annotations, and no output schema, the description is complete. It explains the action, all parameters, behavioral nuances, and return values (updated media list and written file). There are no obvious gaps in understanding what the tool does.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must compensate. It explains resource_type values ('bitmap' | 'font' | 'raw'), defines prep_target with examples ('emery', 'menu-icon'), clarifies that source can be base64/data URI for bitmaps, and meaningful context for dir and name. This fully compensates for the lack of schema descriptions.

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 states the tool's action with a specific verb and resource: 'Add a resource to a project and register it in package.json.' It further details that it copies source into resources/ and updates the media list, distinguishing it from sibling tools like image_prep or project_set_meta.

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 description provides clear context: you use this tool to add resources to a project, and it explains optional preprocessing via prep_target. It does not explicitly mention alternatives or when-not-to-use, but the behavior is clear enough for an agent to infer appropriate usage.

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