Skip to main content
Glama

scan_manuscript_markers

Identify all TODO, FIXME, DRAFT, TBD, and XXX markers in manuscript markdown to flag incomplete sections and pending tasks.

Instructions

Find TODO/FIXME/DRAFT/TBD/XXX markers in manuscript markdown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • FastMCP tool registration for scan_manuscript_markers. The @mcp.tool() decorator registers it. The handler delegates to workflow.scan_manuscript_markers().
    @mcp.tool()
    async def scan_manuscript_markers() -> str:
        """Find TODO/FIXME/DRAFT/TBD/XXX markers in manuscript markdown."""
        try:
            return workflow.scan_manuscript_markers()
        except ValueError as e:
            return str(e)
  • Core implementation: scans all *.md files in the manuscript/ directory for TODO/FIXME/DRAFT/TBD/XXX markers using MARKER_RE regex, counts occurrences, and returns a summary with up to 40 sample lines.
    def scan_manuscript_markers() -> str:
        proj, _ = require_project()
        root = proj.base_path / "manuscript"
        if not root.exists():
            return "No manuscript/ directory."
        counts: dict[str, int] = {}
        samples: list[str] = []
        for path in sorted(root.glob("*.md")):
            text = path.read_text(encoding="utf-8", errors="replace")
            for m in MARKER_RE.finditer(text):
                k = m.group(1).upper()
                counts[k] = counts.get(k, 0) + 1
            for i, line in enumerate(text.splitlines(), 1):
                if MARKER_RE.search(line):
                    samples.append(f"{path.name}:{i}: {line.strip()[:160]}")
        if not counts:
            return "No TODO/FIXME/DRAFT/TBD/XXX markers found."
        summary = ", ".join(f"{k}={v}" for k, v in sorted(counts.items()))
        tail = "\n".join(samples[:40])
        extra = "\n… truncated …" if len(samples) > 40 else ""
        return f"# Markers\n{summary}\n\n{tail}{extra}"
  • MARKER_RE regex constant used by scan_manuscript_markers to match TODO, FIXME, DRAFT, TBD, or XXX (case-insensitive).
    MARKER_RE = re.compile(r"\b(TODO|FIXME|DRAFT|TBD|XXX)\b", re.I)
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the tool finds markers but does not indicate whether it modifies anything, requires specific permissions, or has side effects. The name 'scan' suggests read-only, but this is not 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 a single, concise sentence that is front-loaded with the core action. Every word carries meaning, and there is no wasted text. It is appropriately sized for the tool's simplicity.

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?

Given the tool has no parameters and an output schema exists, the description is reasonably complete. It specifies the markers it scans for. However, it could briefly mention what happens when no markers are found or that it returns a list, but this is not critical for such a simple tool.

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?

The tool has zero parameters with 100% schema coverage (empty schema). According to guidelines, 0 parameters baseline is 4. The description adds no additional parameter information, which is acceptable since there are no parameters to document.

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 clearly states the tool's purpose: finding TODO/FIXME/DRAFT/TBD/XXX markers in manuscript markdown. It uses a specific verb ('Find') and resource ('markers'), and the list of markers distinguishes it from sibling tools that serve different manuscript-related functions.

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 does not explicitly state when to use this tool versus alternatives. While it's implied that it's for scanning markers, there is no guidance on context or exclusions. The tool's simplicity mitigates the need for extensive guidelines, but it remains a gap.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BurgersJackson/storywright-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server