Skip to main content
Glama

Manuscript outline / 生成论文提纲

paper_outline

Manuscript outline / 生成论文提纲 | USE WHEN: the user wants the outline / chapter structure before the full text is written | ALIASES: 提纲, 目录, 章节结构, 论文框架, outline, chapter structure | RETURNS: 章节提纲

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": {
      "title": "<title>"
    },
    "name": "paper_outline"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes论文题目
project_idNo项目 id
design_typeNo研究设计类型

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the agent knows this is a non-destructive generation action. The description adds only the phase context (outline precedes full text) and a terse 'RETURNS: 章节提纲' – nothing about whether the outline is persisted to the project, how long generation takes, or what the chapter granularity/format is.

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?

Front-loaded label followed by clearly labelled USE WHEN / ALIASES / RETURNS segments makes it easy to scan. The long bilingual alias list (提纲, 目录, 章节结构, 论文框架) is padding for a router but still structured, not rambling.

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?

For a three-parameter generative tool with no output schema, the definition never describes the shape of the returned outline beyond '章节提纲', nor whether results persist under project_id. Adequate to select the tool, thin for invoking it confidently.

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%, so title, project_id and design_type are already documented. The description adds no semantics about how design_type influences the outline or whether project_id scopes retrieval of prior context, so the baseline 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?

States a specific verb+resource ('Manuscript outline / 生成论文提纲') and clarifies the scope as chapter/section structure prior to full-text writing, which separates it from full-draft or review tools. It stops short of naming a distinguishing boundary against close relatives such as literature_review_outline, so it isn't fully sibling-differentiated.

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?

'USE WHEN: the user wants the outline / chapter structure before the full text is written' gives a clear triggering condition and implies the ordering (before writing). No when-not-to-use or explicit alternative is offered, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources