Skip to main content
Glama

get_project_status

Retrieve a Markdown table showing the current status of each chapter, including editor verdicts and third-pass completion, to track progress through the writing pipeline.

Instructions

Markdown table of chapters, statuses, editor verdicts, third-pass completion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Core implementation of get_project_status. Requires a loaded project, then builds a Markdown table with columns for chapter number, title, target words, status, editor verdict, and third-pass completions. Returns a string for the MCP tool.
    def get_project_status() -> str:
        proj, _ = require_project()
        lines = [f"# {proj.name}\n", f"Genre: {proj.genre}\n\n"]
        if not proj.chapters:
            lines.append("No chapters — use add_chapter.\n")
            return "".join(lines)
        lines.append("| # | Title | Words | Status | Editor verdict | Third passes |\n")
        lines.append("|---:|---|---:|---|---|---|\n")
        for ch in sorted(proj.chapters, key=lambda c: c.num):
            tp = ", ".join(ch.third_pass_completed) or "—"
            lines.append(
                f"| {ch.num} | {ch.title} | {ch.target_words} | {ch.status.value} | "
                f"{ch.editor_verdict or '—'} | {tp} |\n"
            )
        return "".join(lines)
  • Registers the get_project_status FastMCP tool using the @mcp.tool() decorator. The async function delegates to workflow.get_project_status().
    @mcp.tool()
    async def get_project_status() -> str:
        """Markdown table of chapters, statuses, editor verdicts, third-pass completion."""
        return workflow.get_project_status()
Behavior2/5

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

With no annotations, the description should disclose side effects, permissions, or if the operation is read-only. It simply states it returns data, implying it's safe but not explicitly. Fails to add value beyond the obvious.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, straightforward sentence. It is concise and to the point, though it could be more structured (e.g., bullet list of contents) without loss of clarity.

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?

Given zero parameters and an output schema, the description is minimally complete. However, it doesn't explain the Markdown format or any edge cases (e.g., empty project). Could be more informative.

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?

No parameters exist, so the description needs no additional parameter explanation. Schema coverage is 100% (empty), so baseline is 4. Nothing to deduct.

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 specifies that the tool returns a Markdown table containing chapters, statuses, editor verdicts, and third-pass completion. It distinguishes from siblings like 'get_pipeline_status' by focusing on per-chapter editorial details.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., 'get_chapter_status' or 'get_pipeline_status'). The description only states what it returns without context about its appropriate use cases.

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