open-mcp-apps

Overview Schema Source Related Servers Discussions Admin

App Store live-preview payload (internal)

preview_app_store_entry

Read-onlyIdempotent

Fetch App Store entry details and mock data to render a live sandboxed preview card. Read-only; intended for internal app rendering, not direct calls.

Instructions

Internal: returns an App Store entry's ui and manifest plus its mock-data fixtures, so the App Store app can render a LIVE sandboxed preview card (srcdoc + stub oma + mock snapshot). Read-only; nothing is installed. Not useful to call directly.

Input Schema

Name	Required	Description	Default
`name`	Yes	App Store entry name (see app_store_list)
`locale`	No	sample data language (default en)

Output Schema

Name	Required	Description
`html`	Yes	the entry's ui slot (field named for its format — the preview iframe srcdocs it)
`name`	Yes
`title`	Yes
`category`	Yes
`fixtures`	Yes	embedded mock snapshot items, or null if the entry ships none
`manifest`	Yes
`description`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.10.1Oct 18, 2026

addedInput schema / properties / locale

Added value: +{
+  "description": "sample data language (default en)",
+  "enum": [
+    "en",
+    "zh"
+  ],
+  "type": "string"
+}

Addedv0.7.2Oct 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive, but the description adds real value beyond them: the sandboxed srcdoc + stub oma + mock snapshot rendering model and the explicit 'nothing is installed' assurance. It does not discuss payload size or failure behavior.

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?

A single dense but front-loaded sentence that leads with 'Internal' and the return payload. The parentheticals (srcdoc + stub oma + mock snapshot) are slightly heavy but each carries meaning.

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?

With an output schema present, the description needn't document return values, and it still sketches the payload shape. Combined with full annotation coverage and 100% param coverage, an agent has what it needs to decide not to call it directly.

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 description coverage is 100%, so name and locale are already fully documented, including the enum and default. The description adds no parameter-level meaning, which is the expected baseline when the schema does the work.

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?

States a specific verb (returns) plus a precise resource (an App Store entry's ui, manifest and mock-data fixtures), and frames it as an internal preview payload. This clearly separates it from siblings like install_from_app_store and get_app.

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 closing sentence 'Not useful to call directly' is an explicit when-not signal that most definitions lack, and 'Internal' clarifies the intended caller. No alternative tool is named for agents that do want store data, so it stops short of full routing guidance.

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