Skip to main content
Glama
science-ai-mcp-server

science-ai-mcp-server

by SelfPy

Get Article Writer Pipeline Status

get_writer_pipeline_status

Returns the current writer-pipeline job status for a session and section, enabling polling after starting a writing job and detecting done, failed, or aborted.

Instructions

Not available with an API key during the Article Writer's private beta (the server answers every API-key call with 404). Once the writer is public: return the latest writer-pipeline job for a (sessionId, section). Use after start_writer_pipeline and poll every 5-10 seconds. Terminal statuses: 'done', 'failed', 'aborted'.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "get_writer_pipeline_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNo
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

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 and discloses non-obvious behavior: the beta 404 for API-key callers, polling cadence, and which statuses terminate polling. It stops short of describing the non-terminal status values or what happens for an unknown sessionId, so the agent still lacks a complete picture of responses.

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?

Three tight sentences with no filler, and the most decision-relevant fact (the beta 404) is front-loaded so an agent avoids a wasted call. Slightly compressed punctuation around the poll instruction, but nothing that costs comprehension.

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 two-parameter polling tool with no output schema and no annotations, the definition covers availability, sequencing, cadence, and termination conditions. The remaining gap is return-value shape beyond the terminal status names, which matters somewhat given there is no output schema to fall back on.

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 0%, so the description must compensate; it names both parameters and ties them to the lookup semantics ('latest ... job for a (sessionId, section)'). However, it never explains that `section` is optional or what omitting it returns, and adds no meaning beyond the enum already in the schema.

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 — 'return the latest writer-pipeline job' — scoped to a (sessionId, section) pair, and explicitly positions it relative to the sibling `start_writer_pipeline`. An agent can distinguish it from the start/launch tool without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('Use after `start_writer_pipeline`') and an operational cadence ('poll every 5-10 seconds'), plus the terminal statuses that signal stopping. It also states a hard when-not: every API-key call returns 404 during the private beta.

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