Skip to main content
Glama
Sign In
MCPBridge Server

MCPBridge Server

by RBG-WebDesign
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

title_manifest_create

Create a JSON title manifest from screen boxes, frame timing, and style metadata, saving the output to Saved/MCP/titles for use in Unreal Engine.

Instructions

Create and persist a JSON title manifest using normalized screen boxes, frame timing, and style metadata. Stores output in Saved/MCP/titles by default.

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": {
      "cues": "<cues>"
    },
    "name": "title_manifest_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
fpsNoSequence frame rate, default 29.97
cuesYesTitle cues with normalized box values
styleNo
manifestNo
gapFramesNoGap between auto-scheduled cues
resolutionNoDesign resolution, default [1920, 1080]
output_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the key side effect of persisting output to Saved/MCP/titles by default, but does not mention overwrite behavior, return values, or any validation process. This is moderate disclosure for a create/persist tool.

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?

Two sentences, both informative and front-loaded with the primary function and default output path. No wasted words or redundant details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 8 parameters and nested objects, the description provides only a high-level overview. It does not clarify return values (no output schema) or the relationship between top-level parameters and the nested 'manifest' object. It covers the essential purpose and default path but leaves gaps for a complex creation tool.

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 50%, and the description adds a high-level summary tying together normalized screen boxes, frame timing, and style metadata. However, it does not explain individual parameters or the relationship between 'cues' and 'manifest' beyond what the schema already provides.

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 uses specific verb 'Create and persist' and identifies the resource as a 'JSON title manifest'. It also mentions key inputs (normalized screen boxes, frame timing, style metadata) and default output path, clearly distinguishing it from sibling tools like adjust or validate.

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 usage for creating and persisting manifests but provides no explicit when-to-use guidance or alternatives. It does not mention when not to use it or how it relates to sibling tools like title_manifest_adjust or title_manifest_validate.

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

Deploy Server

Other Tools