Skip to main content
Glama

Play Preview

play_preview
Read-only

Open a limited browser preview of a complete invention document: the piece plays in the user's browser after they tap Play, with a reduced feature set, and may drop out. Use it only when no local Fyug tools are present; when they are, play the piece with them instead. Pass json as a serialized JSON string of at most 64 KiB. The document gets check_invention's check first and fails with the same error; it also fails, naming what it used, when it needs something the browser preview lacks (a bundled development or sample, or a module type its engine does not build). Succeeds with {playable, version, module_count, connection_count}. Nothing is stored.

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": {
      "json": "<json>"
    },
    "name": "play_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
jsonYesComplete invention JSON string (with modules, connections, etc.), at most 64 KiB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past readOnlyHint=true: it discloses the reduced feature set, the possibility of drop-out, the 64 KiB cap, that nothing is stored, that validation is delegated to check_invention with the same error, and the specific failure mode where a bundled dev/sample dependency or unsupported module type is named. It also enumerates the success payload keys, which is essential given no output schema exists.

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?

One dense, correctly front-loaded paragraph: the verb and scope come first, then the usage rule, then the parameter constraint, then failure and success behavior. Every clause carries information an agent needs; nothing is padding.

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?

Comprehensive for a read-only preview tool with no output schema: return keys, failure modes, storage semantics, and size limits are all covered. The only soft spot is that it doesn't say what the preview does with an invention that references external assets other than through the 'browser preview lacks' failure case.

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 coverage is 100%, so the schema already documents the single 'json' parameter and its 64 KiB limit; the description largely restates that constraint. It does add meaning by insisting the value be a *complete* invention document that will be run through check_invention's validation, which shapes what the caller must supply.

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 and resource ('Open a limited browser preview of a complete invention document') and immediately scopes it as a reduced-capability rendering that may drop out. An agent can distinguish this from check_invention or the describe_* siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit selection rule: 'Use it only when no local Fyug tools are present; when they are, play the piece with them instead.' That is a clear when-to-use and when-not-to-use with the preferred alternative named, not merely implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources