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

beat-mcp-bridge

by tholtman1-del
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Get full screenplay text

beat_get_text

Retrieve the complete Fountain text of a Beat document to read or rewrite the full screenplay content.

Instructions

Get the complete Fountain text of a Beat document.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "beat_get_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
docIndexNoIndex into the list returned by beat_list_documents. Omit to target the frontmost/current document.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the disclosure burden. It signals a read operation via 'Get' and specifies the returned content (complete Fountain text), but it does not add details about error behavior, the effect of omitting docIndex, or any other side effects. This is adequate for a simple getter but not rich.

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 a single, tightly worded sentence with no filler. The core action and object are front-loaded, and every word earns its place.

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?

For a one-parameter read-only tool, this description is nearly sufficient. It identifies the exact output ('complete Fountain text'), distinguishes the scope from partial-text siblings, and the schema covers the parameter. It could be more complete by explicitly noting the fallback to the front document, but that is already in the schema.

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%, and the single optional parameter docIndex is already described in the schema. The tool description adds no parameter-level meaning beyond what the schema provides, so the baseline score of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves the complete Fountain text of a Beat document, using a specific verb and resource. It is distinguishable from sibling tools like beat_get_scene_text or beat_get_outline because it says 'complete Fountain text,' though it does not explicitly name those alternatives.

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?

Usage context is implied rather than explicit. The description makes clear this is for getting the full document text, which implies it should be used instead of scene-level or outline tools, but it offers no explicit when-to-use or when-not-to-use guidance.

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