Skip to main content
Glama
Sign In
beat-mcp-bridge

beat-mcp-bridge

by tholtman1-del
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Rewrite one scene

beat_replace_scene

Replace a single scene's text in a Fountain screenplay by its index, preserving all other content. Provide new scene text including the heading to update it in the Beat app.

Instructions

Replace a single scene's text in place (heading through the line before the next scene), identified by sceneIndex from beat_get_scenes. The rest of the script is untouched.

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": {
      "sceneIndex": "<sceneIndex>",
      "text": "<text>"
    },
    "name": "beat_replace_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesNew Fountain text for this scene, including its scene heading.
docIndexNoIndex into the list returned by beat_list_documents. Omit to target the frontmost/current document.
sceneIndexYesIndex from beat_get_scenes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/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 of behavioral disclosure. It clearly communicates the side effects: in-place replacement, the exact replaced region, and no changes to the rest of the script. It does not discuss reversibility or error behavior, but the core destructive semantics are explicit.

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 tight sentences that state the action, the exact span, the identifier source, and the non-effect on the rest of the script. There is no filler and no redundant restatement of the title.

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

Completeness5/5

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

For a small, well-schematized mutation tool, the description is complete: it tells the agent what gets replaced, how the target scene is identified, and what is left untouched. The optional docIndex and required text format are already covered by the schema, and no output schema exists to document.

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?

The input schema already fully documents all three parameters with 100% coverage, including that text must include the scene heading and that docIndex defaults to the frontmost document. The description repeats only the sceneIndex source from beat_get_scenes and adds no new parameter-level syntax, so the baseline score applies.

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 ('Replace a single scene's text in place'), defines the exact span ('heading through the line before the next scene'), and clarifies that the rest of the script is untouched. This clearly distinguishes it from beat_set_text, beat_insert_text, and beat_append_text.

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 establishes the intended use: modify one existing scene by sceneIndex from beat_get_scenes, not insert, append, or replace the entire script. It lacks an explicit named alternative or 'when not to use' clause, but the single-scene scope and 'rest untouched' give clear routing context.

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