pebble-mcp

Overview Schema Source Related Servers Discussions Admin

store_app

Fetch full metadata for a Pebble appstore app or watchface by its ID, including author, compatibility, release notes, download URL, and screenshots.

Instructions

Full metadata for one appstore app or watchface by its id.

Returns hearts, author, description, the list of compatible hardware platforms (with a has_emery convenience flag), the latest release (version + date + notes), the direct .pbw download URL, and screenshot/header image URLs.

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": {
      "app_id": "<app_id>"
    },
    "name": "store_app"
  }
}

Input Schema

Name	Required	Description	Default
`app_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations provided, the description must disclose behavioral traits. It lists the return fields in detail (hearts, author, platforms, release, download URL, images), indicating a read-only metadata operation. However, it does not mention potential errors, authorization requirements, or any side effects beyond the obvious read-only nature.

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 two sentences, front-loaded with the core purpose, followed by a concise list of returned data. Every sentence adds value, with no filler or 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?

Given a single required parameter, an existing output schema, and a simple return structure, the description covers the primary invocation and the key data points. It could mention where the app_id comes from or what happens for invalid IDs, but it is generally complete for a metadata lookup tool.

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 coverage is 0%, so the description must add meaning to the single parameter app_id. It says 'by its id' but does not provide any format, example, or where to obtain the ID. This is minimal compensation for the schema's lack of documentation.

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 opens with 'Full metadata for one appstore app or watchface by its id', a specific verb+resource that clearly distinguishes this tool from siblings like store_search or store_developer. It explicitly states the single-item lookup by ID, making the purpose unambiguous.

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 implies when to use it (when you have a specific app id) but does not explicitly contrast it with alternatives or list exclusions. The sibling tool names (store_search, store_collection, etc.) further clarify the context, but an explicit 'use this instead of...' would strengthen this dimension.

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