pebble-mcp

Overview Schema Source Related Servers Discussions Admin

project_set_meta

Modify a project's Pebble metadata in place: set UUID, adjust target platforms, replace capabilities/message keys, and get the updated block.

Instructions

Edit a project's pebble metadata block in place.

uuid sets a specific UUID (or the literal "new" to generate a fresh uuid4). add_platforms / remove_platforms adjust targetPlatforms (validated against the seven known platforms, kept in canonical order). capabilities and message_keys replace those lists wholesale. Returns the updated pebble block.

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>"
    },
    "name": "project_set_meta"
  }
}

Input Schema

Name	Required	Description	Default
`dir`	Yes
`uuid`	No
`capabilities`	No
`message_keys`	No
`add_platforms`	No
`remove_platforms`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses in-place editing, validation against seven known platforms, canonical ordering, and that capabilities/message_keys are replaced wholesale. It also notes the return value. Missing details like error behavior or prerequisites, but overall strong.

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 concise, front-loaded with the core action, and each sentence adds meaningful detail about parameter behavior. No fluff or repetition.

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?

Given the 6 parameters and no output schema or annotations, the description covers the key behaviors: what each parameter does, validation, and return value. It omits prerequisites (e.g., valid project directory) and error handling, but for a focused mutation tool it is largely complete.

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 description coverage is 0%, so the description must compensate. It explains the semantics of uuid (including the 'new' literal), add/remove_platforms (validation and canonical order), and capabilities/message_keys (wholesale replacement). The required 'dir' parameter is not explicitly described, but the name is somewhat self-explanatory.

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 edits a project's 'pebble' metadata block, using a specific verb ('Edit') and a specific resource. It distinguishes from sibling tools like project_info (read) and project_new (create) by focusing on modification of an existing metadata block.

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 use for editing existing project metadata, but does not explicitly state when to use this tool over alternatives or provide exclusions. It lacks direct guidance on when not to use it, though the context is reasonably clear from the parameter descriptions.

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